I was curious if there are plans to allow contexts for Priority schemes the same as are used for Custom fields.
We are on Enterprise and would like to use Contexts for priority schemes rather than just create a new custom scheme.
BACKGROUND: Our instance has been the recipient of multiple migrations as my company does a lot of M&A, and as we consolidate our sites from these acquisitions, we tend to get inundated with redundant priorities that HAVE to be used for the time being. The schemes has been a godsend in allowing us to assign specific priorities, as several of these migrated sites use oddball priorities (some I believe were actually statuses that were in their Priorities list!).
We are narrowing down our priorities to 4 schemes:
All of these have a "Not prioritized" option which is the default.
We do have some projects with customized priorities, which is fine, but for one project, they want "P3" for the default, and for another, they want "Not prioritized" as the default for the same values. We'd like this feature to eliminate as much of the clutter we already have on our site.
Is there a process improvement to have this enabled? If so please direct me to it.
Hi,
you can take a lool at https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=10440 to see if there is a feature request for this.
what you can do is to set up an automation rule to put the correct priority value in each new ticket.
or create a new priority scheme for each project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.