+ Add Question

Why are 'relative dates' stored with tasks, rather than absolute dates?


I'm a new Premium user, and I'm very happy with Todoist so far - except for one annoying issue I've encountered:

When I create a task entry in Todoist, and assign the due-date as 'today' or 'tom', I should think this would be converted into an actual date before the entry is stored in the database - but this seems not to be the case. This creates problems when editing an entry on a date other than the one it is created on - for example:

* I create a task on Jan 4th, setting the due-date to 'tom'
* I edit the task name on the Jan 5th, prior to (or after) completing the task
* I re-save the task, but now it has been re-scheduled for completion on the 6th, because the due-date field was still set to 'tom', rather than 'Jan 5th', which was the correct due-date as set on Jan 4th.

I've noticed this behavior - which I'd call a bug - a number of times, as I have been playing with different naming schemes for my task entries. So now my task completion dates are all over the place, for both completed and uncompleted tasks.

As a result, I'm reluctant to use the quick-links for 'today' and 'tom', as they invite problems if any edits are made. The only 'safe' solution is to use the calendar picker, rather than the quick-links - but shouldn't these 'relative dates' be converted to actual dates before they're stored with the tasks?

All responses

Brendon Wadey  staff
Replied on Jan 07, 2014 - 02:22 UTC

Hi Nigel,

Thank you for the suggestion. We will consider changing how "today" and smart options are added in future updates. They are indeed saved as that "Today" so if you edit that on another day, that date changes.