Quote:
|
Originally Posted by Ken Case
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.
|
I should mention that we've considered this approach somewhat already, and the big sticking point has been that we're worried about performance when you have to rerank everything to make room: right now you only have to rerank the other actions in your group (hopefully not more than a dozen or two—which also makes it unlikely that you'll ever have to rerank at all), but in this other system you'd have to rerank every action in your database (including the completed ones, since you want to preserve their order as well) whenever you run out of ranks between two items (which would happen much more often).
Of course, that's not nearly as big a problem if you have a separate priority field rather than using it as the only indication of order. (Maybe an easier path would be to just give people more flagging options, so you can flag something as "high" or "low" priority rather than just "a" priority?)