+ Add Question

Priority Sorting in "Today" View Malfunctioning

Good Morning,

At initial login my "today" view was properly sorted by priority in my Windows application. After bringing up Todoist in my browser the list reordered in a random fashion. I have attempted all previously suggested remedies (clearing the cache, log off/on, etc.) to no avail. I had resigned myself to manually sorting my tasks, but the problem became worse. At creation of a task it is sorted into its proper position within the hierarchy, however if I change the priority level of the task it will move to the top of the page, regardless of the new level selected. Reclassifying the task further has no effect.

I have replicated the problem in the Windows App, Chrome, and IE11. However, if I have my iOS app open at the same time I'm modifying levels my windows-based interfaces will correctly sort the task after a server ping. Once I close the iOS app, the problem continues.

Please let me know if you need further information.

All responses

Brendon Wadey staff
Replied on Feb 28, 2014 - 16:21 UTC

Hi Aaron,

- Is this on the Today view or any date based view?
- Are you moving P1 tasks outside of P1 tasks, as well as due dates out of there area?

As these views now will automatically keep sort types together, P1 with p1, P3 with P3, due dates ordered by date of course. They can not be changed.

Regards,
Brendon.

Aaron Tifft premium
Replied on Feb 28, 2014 - 16:47 UTC

-It's in the today and any date based view.

-No, when manually sorting I'm only doing so within the same due dates. When I change the p level of any existing task it moves to the top, no matter what p level I set.

JD
James Dexter premium
Replied on Feb 28, 2014 - 17:31 UTC

Same thing happened to me today. Priority sorting was working earlier this morning but isn't now. It's happening both in the Windows version and the web version (Google Chrome)

David Trey staff
Replied on Feb 28, 2014 - 20:29 UTC

Hello,

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


Best regards,
David

David Trey staff
Replied on Mar 03, 2014 - 15:34 UTC

Hello,

This issue has now been fixed.


Best regards,
David