Quote:
|
Originally Posted by curt.clifton
Dragging a task to a new position in the list would set its priority slider to the average of its two new neighbors. Thus, rearrangements in context view would "stick".
|
It turns out that this is exactly how we order actions now: each action has a "rank" which is assigned based on its position relative to other actions in the list.
It sounds like the proposed change, then, would be to allow actions to have individual ranks in context view rather than forcing them to only have child ranks within their own project. This would let you interleave actions from different projects in context view, effectively assigning individual priorities to each action (based on their position).