Feeds are not be the best to reflect order. For one, there's not a good way to remove an entry from a feed (really is aggregator-dependent) and any attempt to order them would seem like a bit of a hack.

In Atom feeds, for example, you'd have to change the date on each entry in the list to reflect the new order. By changing the Updated date, you cause most aggregators to mark the entry as unread so, in this example, most entries would be unread.

Am I too pessimistic?

I don't care about the feeds. But I think Track is crippled without the ability to rearrange actions in projects, or at least be able to identify/mark one as the "next" action. Then I only want to see the next actions in my home page.

#692 is related to this one

Updating tickets (#373, #105, #107, #117, #125, #126, #147, #177, #182, #183, #185, #197, #202, #206, #220, #236, #240, #276, #283, #294, #300, #305, #309, #312, #317, #324, #337, #357, #358, #360, #433, #452, #462, #17, #74, #82, #92, #123, #265, #431, #440, #475, #94, #256, #258, #464)

Duplicated association with ticket #888 was added

I'd be happy to implement this (if it's really something that the organizers are willing to include). Just let me know if there's been any design/implementation discussion so I don't veer away from something that's already been discussed.

BTW, my interest in this is due to the fact that Shuffle supports ordered tasks under projects. Thus, it would be extremely nice if Track matched this app's specific capability.

I am willing to merge a patch for this. There are drag-and-drop handles on todos, they are currently in use for depedencies and for dragging and dropping between contexts.

It will require a migration to add position to the table, look at the project and context model to keep the implementation of reordening consistent with those.

Updating tickets (#17, #47, #49, #83, #91, #97, #103, #107, #117, #125, #126, #175, #177, #183, #188, #197, #206, #211, #236, #240, #276, #294, #295, #305, #309, #312, #317, #324, #355, #357, #358, #371, #373, #393, #434, #452, #478, #503, #507, #535, #564, #565, #568, #569, #571, #572, #636, #668, #682, #686, #692, #715, #736, #741, #759, #773, #782, #783, #800, #828, #837)

Migrated to GitHub issue #294