taskwarrior icon indicating copy to clipboard operation
taskwarrior copied to clipboard

[TW-1867] Computation of new due/wait dates in recurring tasks does not take DST changes into account

Open taskwarrior opened this issue 7 years ago • 2 comments

Michael Meier on 2016-11-02T18:32:19Z says:

When adding a task in a locale with DST during said DST, the wait: and due: dates for new child tasks after the end of DST are set to 1 hour too early.

Example:

  • Task with say weekly recurrence, set to due:tuesday, wait:tuesday
  • Task added during DST in 2016 in Germany, say in September
  • The wait/due dates would have a time of 00:00
  • Now, fast forward to Sunday, October 30th. The due/wait dates for new tasks are now set to one hour too early, in our example to monday, November 1st, 23:00 instead of November 2nd, 00:00, as it would have been before the end of DST at 03:00 on October 30th.

Naturally, the above dates would vary depending on locale and year.

The same problem also occurs the other way around, when a recurring task was added during standard time. Then, new task's due/wait dates would be set an hour too late.

taskwarrior avatar Feb 14 '18 20:02 taskwarrior

Migrated metadata:

Created: 2016-11-02T18:32:19Z
Modified: 2017-01-17T01:32:45Z

taskwarrior avatar Feb 14 '18 20:02 taskwarrior

Paul Beckingham on 2017-01-17T01:32:45Z says:

I think I have a solution for this in 2.6.0.

taskwarrior avatar Feb 14 '18 20:02 taskwarrior