+ Add Question

Bug postponing recurring tasks on mobile

Since the latest iOS update when I postpone a recurring task by dragging it to "Tomorrow", the task gets moved to the next recurrence date instead.

I only see this behavior on mobile; the web client still works as expected.

All responses

Brendon Wadey staff
Replied on Mar 24, 2014 - 02:39 UTC

Hi Scott,

Please clarify. So if your task is "every thursday" and you move it to Friday, it gets moved to the next Thursday instead?

Regards,
Brendon.

LC
L cs premium
Replied on Mar 24, 2014 - 03:08 UTC

Same here after updating 2 days ago. Basically the 6 buttons under "Schedule" does not function like they should anymore. And after trying a few times with the buttons, the app closes and has to be relaunched.

Brendon Wadey staff
Replied on Mar 24, 2014 - 03:29 UTC

Hi,

So you are on the latest iOS version, and the latest Todoist version? Does logging out of the app and back in again resolve the issue?

Thanks,
Brendon.

LC
L cs premium
Replied on Mar 24, 2014 - 03:51 UTC

Yes, both versions are latest. Logged out, fully closed the app, and logged in again, but no difference. Using the 6 buttons will always end up with the same day that was set. If it is set to "every thursday", it will remain a Thursday in the future no matter what day the reschedule is.

Brendon Wadey staff
Replied on Mar 24, 2014 - 05:05 UTC

Hi,

Thanks, we are looking into the issue now.

Regards,
Brendon.

S
Silvia
Replied on Mar 24, 2014 - 08:00 UTC

Same here. I've just tried to postpone a bunch of due and overdue tasks to tomorrow and now there all set to their next due date.
Quite confusing and now I'll have to dig through all my tasks to see what I planned to do.
I relied on Todoist to manage my todo list, and now its all messed up.

Best wishes
Silvia


S
Silvia
Replied on Mar 24, 2014 - 08:46 UTC

In addition, I just saw that some of the repeating tasks now are due at 23:59 or 0:01 after postponing - without me setting that due date.

David Trey staff
Replied on Mar 24, 2014 - 13:40 UTC

Hello Silvia,

Please clarify - what exact icon did you use? There's a difference between "schedule" and "postpone". If you use the schedule option, you can set the task's date to tomorrow, today, next week etc. without affecting its recurrence pattern. If you use the "Postpone" option, then it will indeed move it to the next occurrence.

As for the due time - do you have the correct time zone set on your devices and within Todoist? Also, whet was the exact due date and/or time of one of the affected tasks so we can reproduce this issue based on your description?


Best regards,
David

S
Silvia
Replied on Mar 24, 2014 - 15:10 UTC

Hello David!

I was using "schedule to tomorrow" - with the icon marked as "Morgen". The second from the left on the top row.
I'm very sure I didn't use "Aufschieben", which would be in the bottom row.

Besides, the schedule for tomorrow worked until the update.

And yes, I've got the correct time zone on all my devices.

What I did was try to reschedule abour 20 tasks for tomorrow. As it was affecting about 20 tasks, the due dates were very mixed - but all of those tasks were scheduled for today somewhere in the past, either by becoming due or by rescheduling.

I had to manually check all my projects and tasks to find the tasks again, and it's not been a task I'd like to do again.

To reproduce the problem, I've been trying to set up a recurring test task thats due in the past (I choose 20.1.2013 and "every 23 days" and trying to schedule it to "tomorrow".
And now its scheduled for the 17.4.2014 which is not tomorrow. It's certainly a hint in the direction, isn't it?

Best wishes
Silvia





S
Silvia
Replied on Mar 24, 2014 - 15:17 UTC

Hello David!

I've found out something else:

I've set up one more of my testtasks - due on the 20.1.2013 and repeating "every 23 days" .

The I choose "Aufschieben" - that would be postpone.

For a very short time, the task was set to the "16.Apr @ 0:00", and then it reverted back to "15.Apr".

Hope that helps.

Best wishes
Silvia

Brendon Wadey staff
Replied on Mar 24, 2014 - 15:56 UTC

Silvia,

This should be fixed in the upcoming update, 8.1.1.

Regards,
Brendon.

S
Silvia
Replied on Mar 24, 2014 - 16:01 UTC

Hello Brendon,

Thats great news! Will you keep us informed when it will be available?

Best wishes
Silvia

Brendon Wadey staff
Replied on Mar 24, 2014 - 16:15 UTC

Silvia,

Your app should auto update. Though we will try to post back when it is released :)

Thanks,
Brendon.

S
Silvia
Replied on Mar 24, 2014 - 16:48 UTC

Hello Brendon,

Thanks for the good news.

I've tried my test task in the web version (running firefox) and I've stumbled over that rescheduling to today will work there, but not rescheduling to tomorrow or next week.
Is that problem known or should I try and describe it in a different thread?

Best wishes
Silvia

Scott Williams premium
Replied on Mar 24, 2014 - 20:07 UTC

Brendon - Sorry for the delayed response to your reply. To clarify, that's exactly what happens. If my task is "every thursday" and I move it to Friday, it gets moved to the next Thursday instead.

Per this thread it sounds like this is getting addressed in your next release, yes?

Brendon Wadey staff
Replied on Mar 24, 2014 - 20:09 UTC

Scott,

It's addressed and being looked into, it should be in the next release. If not, then it will of course be fixed asap.

Regards,
Brendon.

S
Silvia
Replied on Mar 26, 2014 - 16:47 UTC

Hello Brandon, hello David,

It looks like the bug on the iOS devices is fixed with the update to 8.1.1.

Thank you.

Best wishes
Silvia

LC
L cs premium
Replied on Mar 27, 2014 - 02:36 UTC

After yesterday's update it's much better although there is still a small bug with one of the 6 buttons; "Pick date and time".

Two scenarios:
1. A repeating task that has date & time set, eg. ev 27 @ 9am, upon using this button, it correctly sets the new date but automatically sets the time to 11:59pm instead of keeping it at 9am. The other 5 Schedule buttons keeps the time at 9am.

2. A non-repeating task set at eg. 27 @ 9am, using this button only changes correctly to the new date but time disappears altogether, nor does it suggest a new time such as 11:59pm.

David Trey staff
Replied on Mar 27, 2014 - 13:14 UTC

Hello L,

Thank you for your report, I've been able to reproduce this and have passed it to the developers.


Best regards,
David

paolo russo premium
Replied on Apr 05, 2014 - 08:30 UTC

I experience a very similar bug on Todoist 4.1.5(147) for Mac.
If I set a recurring date writing "every day starting Apr 5 at 09:00am", the date is set correctly, but the time is set at 11:59pm invariably. Of course, the bug does not depends on the time I choose for this example.
Todoist 8.1.1 does not show the same bug, but:
1. If I create the above item on my iPad, it shows on my Mac the right way;
2. if I create the above item on my iPad and then I edit it on my Mac (changing the time to 9:10am for example), the item is automatically postponed by 1 day.
2. If I create the above item in my Mac, it will keep the time to 11:59pm on both platforms even if I try to edit it on my iPad.

Best,

Paolo

MM
Mike M premium
Replied on Apr 05, 2014 - 19:27 UTC

Hi @Paolo,

I've created myself a new entry for the issue you're facing too - https://todoist.com/Support/show/31579/ - let's address it with Todoist staff there and leave this topic to be treated separately.

Best wishes,
Mike

paolo russo premium
Replied on Apr 05, 2014 - 20:30 UTC

Hi @Mike,

I am copying my post under the thread you suggest.

Best,

Paolo

David Trey staff
Replied on Apr 06, 2014 - 20:44 UTC

Hello Paolo,

This is caused by the incorrect due date format - you're adding a time to the starting date instead of the actual due date of the task.

That said, instead of "every day starting Apr 5 at 09:00am", please use "every day at 9am starting Apr 5".


Best regards,
David

paolo russo premium
Replied on Apr 07, 2014 - 07:09 UTC

Hello David,

thanks for your advice. I stand corrected.

However, Todoist should issue a "Invalid date" message as in any other case of wrong syntax rather than generating a random timing. It is a bug that you have to address.

Thanks,

Paolo