tickets should have ranked priorities

[anonymous]

When delving into the project management side of track, I've begun paying more attention to the ticket priority settings. For each user, I've been trying to adjust the priorities of their tickets so that they can easily see which tickets should be resolved first.

It would be nice if I could rank tickets based on their priorities, such that the highest ranked open ticket would have a priority of "highest". Once that ticket was resolved, the next highest ranked ticket would become the new "highest" priority ticket. So, one could rank the tickets: 1,2,3,4,5,… and as each ticket is resolved, the next one is clearly identified as the "highest" priority.

This way a project manager could go through all the tickets once, set the priority ranking and then the "highest" priority ticket would get updated automatically.

As it stands now, once the highest priority ticket is resolved, it is not always clear which is the next highest. Really, there should alway be only one "highest" priority ticket for a given user. There might be several "high" priority tickets, but which one is the next in line after the "highest" priority?

[Christopher Lenz]

The priority field is there to help you keep track of the importance of tickets. The exact order in which you should work on tickets is something you (and/or the project team) should judge based on the available information and the project roadmap.

I don't think that we should be storing every tickets importance related to the other tickets, and I don't see how that would work, or even scale to a couple hundred tickets.