Different ways to assign Priority?
It seems that there is one list of Priorities that is shared by all the types of records, tickets, projects, changes, etc. We have settled on using 3 levels of priority for tickets, and really 2 would be fine. But the IT manager would like to have finer-grained settings for things like Projects where there are a couple dozen going on at any one time and using a "low-normal-high" model doesn't work. I created 10 new Priority levels (Project 10, Project 20...Project 100), but it seems kind of odd to have these things all mixed together. Is there a way to have a separate set of Priorities for things other than tickets?