I've just migrated all of my tasks to Doit.im, and I've experienced exactly the same behavior.
After that when I open another project (click somewhere in the left bar) and return to the project I added task to, the order is correct again and the new task is on second position. I can get used to it, but the problem is annoying and if i try to sort the tasks right after I added the new task, everything is ruined because the indexes seems to be messed up.
Thank you
I love you product :)
-
01/23/2014 02:12#2PRO
-
01/23/2014 04:05#3PRO
@darekkay @zajacm2
Hi,
Which browser do you use?
Is it in every project or only in some? The list you point to is next group,right? -
01/23/2014 07:46#4PRO
Happens to me, too, in V4. I use Chrome. Yes, Next list only (not Someday or Waiting). And it seems to happen with the N input method, too.
Add a task: total mixup.
Refresh or leave/return: order restored, but new task appears in a random position (often but not always as #2)
Similar results (random placement of new tasks) also happens when you drag tasks from another box into Next.
@wendy_only - when we have discussed related matters before you have said that Doit does in fact have a "pseudorandom" default manual sorting order called "position". As before, I suggest that this "pseudorandom" sorting order be replaced by a more understandable default initial placement of the new tasks, such as priority. -
01/24/2014 10:05#5PRO
@Folke
Hi,
The new task should be the last one before you manual sort it according to our default manual sorting order. If it is pseudorandom, it must be a bug. We have found the cause. We will fix it ASAP. -
01/24/2014 11:39#7PRO
@wendy_only
How is it going with a more "user-friendy" default sorting order (initial placement) instead of the "secret" default order? Have you given up the possibility of doing the initial placement by priority? Have you decided to place tasks consistently at the bottom now?
If priority placement is not possible, or will take a bit longer to implement, I would suggest that initial placement at the very top is much, nuch better than initial placement at the bottom, because you then see the tasks immediately and can correct their placement if you do not like it.
Also, the newer tasks are usually more important. If the old ones at the bottom had been important you would have done them already ;-) So the bottom is a "dangerous" place to put the new tasks, from both points of view. -
01/25/2014 03:36#8PRO
@Folke @darekkay @zajacm2
Hi,
Please refresh your web page to have a check. -
01/25/2014 10:20#9PRO
@wendy_only
It seems that now, when you create a new task while on the Next list, it lands at the bottom, and when you create the tasks on another list (e.g.) and the move it to next at lands second from the top.
What I would prefer would be:
- consistent behavior, regardless of whether the task was initially created on that list or moved to it from another list, and I would prefer this consistent initial placement to be:
Alt 1) Immediately before the highest ranked existing task of the same priority,
or, in the interim, until this can be implemented:
Alt 2) At the very top -
01/25/2014 11:39#10PRO
@wendy_only
... or, if Alt 1 cannot be implemented for quite some time:
Alt 3) Reinstate the old automatic priority sorting.
Manual sorting or adjustment on the Next list is not nearly as important as having the convenience of the automatic priority positioning, so I we cannot have both, then the old system was better than the new one.
Manual sorting would be much more useful on some other lists, for example on the Today list, for example when grouped by Context, if you could then order your Errands in the order you will visit different parts of town. and order your Calls in the order you intend to make them. That would be very meaningful. -
01/27/2014 09:12#11PRO
Seems it's working fine again. Awesome, thank you.