+ Add Question

Problems with postponing a repeating task

S

When postponing a repeating task past the repeat date, and you then complete it, its due date is set to 2015. Month an day are what would be correct for the repeat, but the year is 2015 instead of 2014.
It seems the postpone function can't generate a task thats past due and can't skip a repeat instance.

Could you verify?

Thanks in advance.
Silvia

All responses

David Trey staff
Replied on Feb 04, 2014 - 13:24 UTC

Hello Silvia,

Please tell me:
- What's the exact due date of the task?
- When was it postponed (as it was overdue by a day, as it was due today etc.)?
- Which postpone option did you use (tomorrow, in a week...)?


Best regards,
David

S
Silvia
Replied on Feb 04, 2014 - 14:34 UTC

Hello David!

The exact due date was the 2nd of February. The date is supposed to repeat "after 2 days". I used postpone to tomorrow every day until today, when I marked the task done. The next due date was set to 4th February 2015.

Hope that helps!

Best wishes
Silvia

David Trey staff
Replied on Feb 04, 2014 - 16:23 UTC

Silvia,

So, to clarify - the exact due date of the task was "2nd of February", "after 2 days" or "after 2 days starting Feb 2"? Please let me know what exactly did you type into the date field.

I have tried to reproduce this now by setting a task to "after 2 days", schedule it to tomorrow and check it off. When I did, it moved to Friday (this year).


Best regards,
David

S
Silvia
Replied on Feb 04, 2014 - 18:12 UTC

Hello David!

The tasks due date was "after two days starting 29 1". I tried to reproduce the problem, but didn't manage to do so.
I think the task has to be postponed several times to produce that error.
I'll take note of the tasks due date next time I postpone something and if the error reproduces, I'll update here.
Thanks for the support!
Silvia

S
Silvia
Replied on Feb 05, 2014 - 09:14 UTC

Hello David!

I managed to catch the issue - it's the postponing that does the change in the due date.
I have a task thats due "after 20 days starting 15 1". It was in my due yesterday list. I just postponed it to tomorrow, and now its due on the 6th of February 2015. If I check it, its still set to "after 20 days starting 15 1".

It's not possible to recreate the issue by creating a task with a due date in the past - as you have to put "after 20 days starting 15.1.2014" as due date, and then the task postpones perfectly. Somehoe, the "15 1" and the due date of "4 2" generates a 2015 due date.

Could you try and verify that?

Thank you
Silvia

S
Silvia
Replied on Feb 05, 2014 - 09:15 UTC

Hello David!

By the way: This also happens on the web version. It's not only in the iOS version.

Thanks again
Silvia

David Trey staff
Replied on Feb 05, 2014 - 14:39 UTC

Silvia,

Unfortunately, I still can't reproduce this.

Please tell me, are you sure you've postponed it to tomorrow? Please note that the "postpone to..." feature represented by the circular arrow does not postpone the task to tomorrow, but to its next occurrence so when I hover over it with a task due "after 20 days", I will see "Postpone to 25 Feb". Using this option correctly moves it to 25 Feb 2014.

If you use the "More" option (on the web, from the right-click menu), then you will see the sun icon which allows you to postpone it to tomorrow regardless of the task's recurrence pattern.

I've tried that too - on a task from the past and a current task, and even on a task set to the next year to begin with and in each case it gets correctly moved to tomorrow.

That said, as you've mentioned that it can't be reproduced with an "artificially overdue" task (set to start in the past), I will set up a task to "after 20 days starting 5 2" and tomorrow try to postpone it to tomorrow when it becomes naturally overdue, though technically there should be no difference between a task that becomes overdue by itself and one set to start in the past.


Best regards,
David

S
Silvia
Replied on Feb 05, 2014 - 15:08 UTC

Hello David!

I'm sure I postponed it to tomorrow - I specially checked to find a way to document this.

I agree that there must be something in creating an "artificially overdue task" that changes the behaviour.
Or there might be the possibility that the task needs to be due in its repeat cycle - my test task today was due "20 days after 15 1", making its first repeat due date yesterday. So a test task with a shorter repeat cycle would be a better test candidate.

I'll try again tomorrow to see if there is a difference between "postpone to tomorrow" and "postpone/change to today". I've only noticed problems with "to tomorrow".

Thanks again
Silvia

S
Silvia
Replied on Feb 05, 2014 - 15:25 UTC

Hello David!
I've also set up a few test tasks to find out what exactly happens.
I'll report once I see more clearly.
Best wishes
Silvia

David Trey staff
Replied on Feb 06, 2014 - 13:36 UTC

Silvia,

I've postponed to tomorrow all the test tasks I've created yesterday which were overdue today and I still can't reproduce this issue, all of them were correctly rescheduled to tomorrow.


Best regards,
David

S
Silvia
Replied on Feb 06, 2014 - 15:47 UTC

Hello David!

I think some additonal factor has to play into it. I've had quite a lot of tasks suddenly set to 2015 today, this time by using "postpone to next week".
i've set up a test task that I will let repeat one time to get it due on another day than what you see when you check the task.
What I mean is: The task is repeating "after two days starting 6 2" starting today. If I check it off today, it still says "after two days starting 6 2", but its due on the 8 2.
Perhaps postponing it in this state will show the error.
I'll kepp on trying.

best wishes
Silvia

David Trey staff
Replied on Feb 06, 2014 - 17:54 UTC

Silvia,

That's actually the correct behavior. The task will maintain its full date formula even after your complete or postpone it.

Could you please clarify the "quite a lot of tasks suddenly set to 2015 today" part? How did they change exactly? Also upon postponing or did you just add a date to them and then saw how the date changed by itself?

We will soon release an update to our iOS app version 8.0.3 where some sync and date issues are addressed, we hope this will fix the one you're experiencing too.


Best regards,
David

S
Silvia
Replied on Feb 06, 2014 - 17:57 UTC

Hello David!

The tasks that moved to 2015 were all postponed by me. I tried to postpone some tasks to next week - they were moved a bit further into the future...

I think the task has to be in this state - retaining the original date and due on another day - to be affected by the postpone problem.

Let's hope I'm able to reproduce it soon. Or even better, let's hope for the update to fix it!

Thanks for the support - keep up the good work
Silvia

S
Silvia
Replied on Feb 11, 2014 - 10:12 UTC

Hello David!

I'm afraid I can't reproduce the problem. I narrowed it down to the use of "tomorrow" and "next week", but I can't figure out why some tasks are moved to 2015 and some not.
It's a bit frustrating, but I'll keep on watching my tasks and hope to find a commen cause.
Best wishes
Silvia