Reorder next actions
Would it be possible to give users the ability to reorder next actions in the same way that projects can be reordered?
Leave a comment
This is a big piece of functionality that I feel is missing in getting me to easily determine what the true next action is for any given project (though even without this it has been a great success for me in organizing my life). Might I suggest the following sortings:
Home or Context View:
1. Due date
2. Order of action within project (so for a date group all of the true 'next actions' will sort to the top)
3. Project order number (meaning that the top 'next-action' aside from the date sorting will be the one marked as 'next' for the highest project in that hierarchy)
Project View:
1. Order of action within project
2. Due date
This would insure that when looking at a project that I can set the actions in a logical order and they will continue to appear that way within that view regardless of due date though when looking at a summary view (such as contexts view) the date is more important and takes precedence in the sort.
Creation date is less useful (to me) as a sorting mechanism as it has little context to when the action needs addressed.
Thanks again for all of your efforts, they are very appreciated.
Home or Context View:
1. Due date
2. Order of action within project (so for a date group all of the true 'next actions' will sort to the top)
3. Project order number (meaning that the top 'next-action' aside from the date sorting will be the one marked as 'next' for the highest project in that hierarchy)
Project View:
1. Order of action within project
2. Due date
This would insure that when looking at a project that I can set the actions in a logical order and they will continue to appear that way within that view regardless of due date though when looking at a summary view (such as contexts view) the date is more important and takes precedence in the sort.
Creation date is less useful (to me) as a sorting mechanism as it has little context to when the action needs addressed.
Thanks again for all of your efforts, they are very appreciated.
This would also be helpful for inserting a new next action into a project if you didn't think of it when initially setting the project up. I often add a bunch of next actions, then remember one that should be at or almost at the top of the list. I don't see any easy way to add that in tracks right now.
Not sure if this is a new idea, but wouldn't it be possible to have one or more nullable "depends on" field on actions? This would give a clear sorting order at least for actions that have true dependencies on each other. For independent actions, the displayed order may not be that important?
Migrated to GitHub issue #1558