Reorder next actions

[dnrce]

Migrated from the original issue #91 at https://www.assembla.com/spaces/tracks-tickets/tickets/91

Would it be possible to give users the ability to reorder next actions in the same way that projects can be reordered?

Originally reported by Anonymous on July 7, 2005 at 07:57:08 (-0500)

[dnrce]

On August 8, 2005 at 13:45:29 (-0500), Anonymous commented:

There are now Ajax methods which let you drag and drop to reorder lists. However, we'd have to think how to prioritise sorting on due date, creation date etc, or a manual sort order.

[dnrce]

On December 12, 2005 at 13:15:59 (-0500), bsag commented:

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.

[dnrce]

On January 1, 2006 at 03:12:32 (-0500), Anonymous commented:

I'll have a think about this, perhaps when I work on dependencies within project (e.g. #185).

[dnrce]

On April 4, 2006 at 00:15:02 (-0500), Anonymous commented:

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.

[dnrce]

On May 5, 2009 at 17:06:57 (-0500), bohrax commented:

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?

[dnrce]

On May 5, 2009 at 12:35:42 (-0500), lrbalt commented:

the depends on feature is a known enhancement request.

[dnrce]

On May 5, 2009 at 10:09:15 (-0500), bohrax commented:

Related association with ticket #300 was added

[dnrce]

Related to #916 and #937

[dnrce]

See #692 for some related suggestions.