Skip to content

[TW-35] Task Recur does not honour due Time or Wait #97

Description

@taskwarrior

John Warren on 2013-04-01T12:45:57Z says:

I've created lots of recurring tasks (which to be honest was a massive mistake). I have found that when I create a task:

task add VIP thing everyday due:01/04/2013-14:40 recur:daily wait:01/04/2013-14:00

Then I do a task done and task to spawn the next recurrence I find that the newly "spawned" recurring task defaults back to midnight of that day and not to the time it was set for as the due. I it also interesting does change time when for example you have a change to daylight savings time. The result now these task do not default to 00:00 but to 01:00 in the UK at least.

I also note that the wait does not work. Which makes sense in one respect and I have seen lots of posts about this. I was hoping for a wait:due-1d or due-1h operation or a preservation of the relative time difference between due and wait when recur triggered but not to be.

For me this results in tasks due for Friday being respawned on Saturday and then I have to push them to wait to ignore them until Thursday. I'd love to use the wait, scheduled and due as they were intended but I've not quite been able to do this with recurring tasks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions