Group projects by priority | Help Center

Group projects by priority

PRO

alexkdev 02/15/2014 10:11

Platform:Web

As my old post has been buried and is way too long, I start a new one...

WHEN will project grouping by priority be re-implemented ?

Really I tried to handle with manual, it is really a pain in the ass when you have many tasks.

So Doit Team, what is the problem to make a combobox and add to the SQL request a "ORDER BY" clause ???

Explain me, I am sure many here want to know.

wendy_only post on 02/16/2014 08:15#1

PRO

@alexkdev
Hi,

Do you point to the task list under the Project?

Thank you for your support!

Best regards,
Doit.im Team
—————————————
Facebook: http://www.facebook.com/imdoit
Twitter: https://twitter.com/doitim
Help Center: http://help.doit.im/
Blog: http://enblog.doit.im/
Group: http://help.doit.im/group/
alexkdev post on 02/16/2014 15:36#2

PRO

In a project, on the right pane, my tasks are not ordered, and I want to have the ability to sort them by priority, like before.
alexkdev post on 02/16/2014 15:37#3

PRO

This is a private comment.
lisa_alway post on 02/16/2014 19:29#4

PRO

yes please, when???
wendy_only post on 02/17/2014 10:26#5

PRO

@lisa_alway @alexkdev
Hi,

Thank you for your information.

We will consider it seriously.
LongNguyen post on 02/18/2014 07:07#6

PRO

I still don't know why did they take it out from the first place
Folke post on 02/18/2014 11:49#7

PRO

@LongNguyen - I agree it was an unwise decision, and here is my guess for why they did it:

I believe maybe they were trying to accommodate user requests for managing subsequent (not-yet-active) tasks in projects, and had even heard some requests for the very crude solution called "sequential projects" (one task at a time, automatically), and decided that an even shorter shortcut to accomplishing this would be to mandate manual sorting and have the "show one, show all" toggle.for the Next list.

Of course, in reality (and in GTD) projects very often do not have only one next action. There can be several such actions in a project, and all these need to be visible, but typically not all of the tasks in a project are active (next or waiting, done by me or by others). Some tasks really can be done only at some later stage when other tasks have first been completed, and those tasks - only those, i..e the subsequent, dependent tasks - are the ones that should be hidden from the next and waiting lists. To manage this properly, it is necessary to be able to arrange in each project individually which tasks are currently active and which ones aren't, e.g. to have a "line" under which you can drag the subsequent tasks (and place them manually into order there).

Besides, many people use the Project feature for other things than for real projects, as "containers" of all kinds. In these cases, all tasks a generally active.

The automatic priority sorting of tasks was a very strong and useful feature that Doit had before. Extremely convenient on all lists where you do not need an exact manual order, i.e. for most lists. Manual adjustment could always be a nice complement, but manual sorting mainly be necessary as the primary method in a future "subsequent" section of the project that does not exist in Doit yet.
JDavidCarr post on 02/18/2014 22:39#8

PRO

By forcing all tasks to have "Next" as their initial status, it requires the user to manually to change them to something else (and there are no custom choices, or null values) in order to avoid having them all appear as though they are Next Actions. In actuality, almost all of my projects have a single Next Action, and in the event that a project has two or three (your scenario above) I'd prefer to set those two or three tasks to "Next" or "Next Action" manually, rather than have the bunched in with all the other Nexts in the view.

Frankly, spending time setting all my tasks to something other than "Next" (and there are no good options, since the other values have specific meanings that are not interchangable in a GTD-based method) is a huge waste of my time that I could be doing something else, like, well, Getting Things Did. As a result, I now work out of my Today view and I find myself seldom looking in my Next view. This has reduced my feeling of efficiency and led to frustration with my current choice of systems.

Creating tasks as "Next" by default rather than as "Not started" or null, or something similar is one of the few significant shortcomings with Doit.now and probably the only reason I continually review/assess other solutions. If it weren't for the cross-platform availability, this would be enough to have already pushed me away to another system.

Having "Next Action" tasks (or above the line in Folke's scenario) and "Not started" or null-status tasks (below the line in his scenario) would solve this problem and ring true from a GTD perspective. Setting all the tasks to "Next" is utter nonsense.
alexkdev post on 03/15/2014 10:32#9

PRO

@Doit team,

Honestly the way you're making fun of your clients is unbelievable.
Since 3 monthes, your only answer is that "we will consider it seriously".

How many people is working for Doit ?
Are your developers too dumb to put a filter on a SQL request ?
Don't you think a request from your "PRO" clients should be treated with a minimum of service level ?
If a "PRO" customer request goes to thrash then you know where your business is headed.

I am not the only one to be mad about it, seriously.
Think about it...fast.
wendy_only post on 03/16/2014 06:03#10

PRO

@alexkdev
Hi,

Sorry that it has not been in our developing plan yet. We are woking on improving the apps and developing other new features now. We are also recruiting more developers to solve this issue.

If we make this feature,it will take much of time to reconstitution as now all items which can be sorted manually are sorted by Position (an value in programme). Our developers will do a research on this feature and find a better way to progress this issue.
Folke post on 03/17/2014 16:03#11

PRO

@wendy_only - I agree with @alexkdev that this is a very serious matter. Other (entirely new) features generally are not as important as making the existing features complete, well-rounded and useful. Quality is more important than quantity.

Manual sorting is primarily useful on the Today list - so why on earth did you not implement it there (only in the DoitNow section)? And among the "not-yet" (subsequent) tasks in each project (which you do not even support yet, as @JDavidCarr correctly points out).

On the Next list manual sorting can have some value as a nice and attractive complement, but it is totally counterproductive to be forced to sort every task manually. Priority based default placement (newest first) is "necessary" - and if you manage to find a way to make it manually adjustable, too, then it is is an added bonus but not a viable substitute.

This "position" that you keep mentioning does not seem to be based on anything meaningful. I understand if there must be a "position", but this position can be calculated in an endless variety of ways and I suggest you redefine the calculation such that the position defaults to 1) priority, 2) newest-first 3) manual adjustment, if any.