New Priority Schema?
|Reported by:||Owned by:|
|Cc:||Ryan J Ollos||Branch:|
What if, instead of using a fixed, 5 option enumerated priority schema, you just use a numeric, non labeled schema, from 1 to n? This could allow to re-prioritize a ticket easier (with the proper UI, of course).
You just need to inter-change priority values when moving a ticket one position up or down, and when you move it "jumping" n tickets, those should only be incremented or decremented by 1 on their priority field and after that, use the "free" space for the re-prioritized ticket.
You can provide an arrow up / arrow down on the lists for every query, for "one step move", and a more advanced option on ticket edition, like a "give immediate upper/lower priority respect to ticket n[user provided]", for bigger jumps.
I think that the DB impact with this change could be minimal, but you have to re-think some features like the color from red to green on your listings.