+ Add Question

Rescheduling a repeating task fails

S

I noticed a problem with rescheduling repeating tasks with a due date in the web version.

Here's my test task:

It's set to repeat "every 23 days at 16 starting 20 1 2013" - so it's quite overdue.

If I reschedule with the "today" button, it's set to be due today. So far, so good.
If I now reschedule to "next week" - with the button, it's suddenly due on the 31.3.2013.

There's something wrong with the rescheduling. Not only in the iOS version.

Could you please verify?

Thank you.

Best wishes
Silvia

All responses

David Trey staff
Replied on Mar 24, 2014 - 23:46 UTC

Hello Silvia,

This seems correct. Rescheduling doesn't "stack" the dates. If you reschedule a task on Monday to "next week" it moves to next week on Monday which is 31.03.2013, it will not move another week ahead if you do it again.

The schedule option only "sets" one specific date for one specific event and it's an either or choice, not "first set it to tomorrow and then +1 week after tomorrow".

Now, if you complete such task, it will move +23 forward counting from its original date formula.


Best regards,
David

S
Silvia
Replied on Mar 25, 2014 - 05:23 UTC

Hello David!
I'm sorry, but the 31.3.2013 is not next week.
Not even close.
It's 2014.
Could you please check that again?
Best wishes
Silvia

S
Silvia
Replied on Mar 25, 2014 - 07:39 UTC

Hello David!
It looks like that is the same problem like the one I had with tasks suddenly being scheduled for 2015. Day and Month are correct - like in this case - but the year is wrong.
Could you please try and recreate this - I've been having so much trouble with the scheduling lately!
Best wishes
Silvia

David Trey staff
Replied on Mar 25, 2014 - 13:42 UTC

Silvia,

I'm sorry for the misunderstanding, I didn't notice the year. You're right, it moves it to the incorrect date/year, I've passed it to the developers and we'll look into it now. Sorry for the inconvenience.

However, please tell me, does it also happen with tasks that are "naturally overdue"? I've tried it on various different tasks that I already have overdue with similar dates (every 7 days @ something, every 20 days) and these all work fine when rescheduled, only if I specifically add it with a starting date in the past, then it behaves incorrectly.


Best regards,
David

S
Silvia
Replied on Mar 25, 2014 - 14:28 UTC

Hello David!

I took some tests to notice the year, too - and if I remember my 2015 problem, all thos tasks had a correct day and month.

So I think I've seen it happen with "naturally overdue" tasks that have a start date and a due time - but I can't reproduce as I had to reschedule a lot of tasks manually yesterday.

But perhaps the "artifically overdue" task alone is sufficient to find the error.

Best wishes
Silvia


S
Silvia
Replied on Apr 01, 2014 - 06:10 UTC

Hello David!

I see it's not fixed yet - any news on the problem?

Best wishes
Silvia

David Trey staff
Replied on Apr 01, 2014 - 12:33 UTC

Silvia,

This is addressed in version 8.2 which we're testing now and will publish it relatively soon (+ Apple's approval time).


Best regards,
David

S
Silvia
Replied on Apr 01, 2014 - 13:07 UTC

Hello David!

This problem is also happening on the web version - thats were I tested it today. Will it also be fixed there?

Best wishes
Silvia

David Trey staff
Replied on Apr 01, 2014 - 16:41 UTC

Silvia,

Our web devs are looking into this too.


Best regards,
David

S
Silvia
Replied on Apr 08, 2014 - 14:27 UTC

Hello David!

Any news on the problem?

Best wishes
Silvia

David Trey staff
Replied on Apr 08, 2014 - 14:49 UTC

Silvia,

Both the web and the iOS team are looking into it.


Best regards,
David

S
Silvia
Replied on Apr 08, 2014 - 15:26 UTC

Hello David!

Thats good to know. Keep up the good work!

Best wishes
Silvia

S
Silvia
Replied on Apr 28, 2014 - 13:56 UTC

Hello David!

As it's been one month now, and the bug is not fixed yet - any news on the problem?

Best wishes
Silvia

David Trey staff
Replied on Apr 28, 2014 - 14:00 UTC

Silvia,

Our new iOS app has been submitted to the App Store last week, we hope it'll be approved this week.


Best regards,
David

S
Silvia
Replied on Apr 28, 2014 - 14:15 UTC

Hello David!

That's great - I'm really looking forward to it.

As the error occurs in in the web version, too - will it be fixed there soon, too?

Best wishes
Silvia

David Trey staff
Replied on Apr 28, 2014 - 14:25 UTC

Silvia,

It is on our developer's task list, as soon as I have any updates on it, I will let you know and post here once it's fixed.


Best regards,
David

S
Silvia
Replied on Apr 28, 2014 - 14:32 UTC

Now we all hope the developers task list is not too long!

Thank you for the feedback and I'm looking forward to the new iOS version!

Best wishes
Silvia

S
Silvia
Replied on May 28, 2014 - 14:39 UTC

Hello David,

It's been two months now, and the problem is not fixed yet.

Really?

Best wishes
Silvia

David Trey staff
Replied on May 28, 2014 - 15:25 UTC

Hello Silvia,

We're sorry for the delays, it's on our developers' to-do lists, we'll look into this.


Best regards,
David

S
Silvia
Replied on Jul 09, 2014 - 18:39 UTC

Hello David,
It's been over three months. I get the distinct impression that your developers list is too long.
Best wishes
Silvia

TP
Trish Putnam premium
Replied on Jul 09, 2014 - 18:46 UTC

I ran into this last night, as well. It's disturbing, because the only reason I noticed is I happened to go look at my 7 days view immediately after and noticed that the task wasn't on next Monday as I expected. I had to go to the project, find the task and observe that the year was now moved ahead to next year.

If I hadn't happened to look at that time, I quite possibly wouldn't have noticed or remembered the specific task until it caused a problem that I hadn't done it yet. Once again, this is a basic functionality that MUST be reliable. If I have to go check it every time, the software has failed and I can't trust it.

Brendon Wadey staff
Replied on Jul 09, 2014 - 18:48 UTC

Hi,

We are very sorry for the delay, this fix should be in our next update, which should be coming very soon.

Regards,
Brendon.