Description
The Priority feature looks good and promising, but the way I am trying to use it, it doesn't feel very useful.
In my project I currently have 3 priority outcomes, which correspond to successive milestones, let's call them A, B, and C. A is a child of B is a child of C, and the priority is A > B > C. Each has a bunch of children. I was hoping that by setting these priorities, all children would have that priority associated with them, i.e. in the table view there would be some way for the highest priority Smalls to bubble to the top, and for this priority ordering to be mixable with other filters like Status.
Namely I would expect all children of A to be at the top of the table, followed by all children of B not associated with A, followed by all children of C not associated with B, followed by all outcomes not associated with C.
What do you think of this, conferring priority to children? Or is it intended to be used at a more fine-grained level than that?