Open taskwarrior opened 6 years ago
Migrated metadata:
Created: 2013-04-09T02:50:33Z
Modified: 2014-06-25T02:19:54Z
Ralph Bean on 2013-04-09T03:01:07Z says:
"kostajh":https://github.com/kostajh and I ran into the need for this when trying to port the python "taskw":https://github.com/ralphbean/taskw lib from manipulating the @~/.task/*.data@ dbs to using taskwarrior commands as per "the 3rd party application guidelines":http://taskwarrior.org/projects/taskwarrior/wiki/3rd-Party_Application_Guidelines
Tools that use taskw expect to be able to enter custom dates for annotations. Notably, "bugwarrior":https://github.com/ralphbean/bugwarrior tries to sync comments on tickets in ticket systems that occurred in the past.
David Patrick on 2013-04-12T21:59:31Z says:
That parameter is called "entry", isn't it? (update: no it isn't)
How about treating it like other attributes/ annotations, with something like;
$ task 142 timestamp:2013-14-02-16:30:00
This might throw an error if "no annotations found". If 142 has more than one annotation, a message "this will modify timestamps for 3 annotations. y/n" might be used. To modify a specific annotation among several, the same rules as denotate might apply, so that the first partly matched annotation is modified.
food for thought
Paul Beckingham on 2013-04-13T13:22:43Z says:
That parameter is called "entry", isn't it? (update: no it isn't)
Right. It's called "entry" in the JSON version. Otherwise, just part of the annotation name.
I think this would be achieved by adding a helper command, something like this:
task_annotate
Paul Beckingham on 2013-09-07T17:04:47Z says:
I don't have an acceptable solution to this. Need more thinking.
Paul Beckingham on 2013-04-09T02:50:33Z says:
Annotation time stamps are generated from the clock, and are not overridable. It would be useful to be able to specify the time, although not by default, as the annotations are used for "logging".