Hi Whip,
You could always create custom single select lists for each of your projects and use those to indicate the project custom priority. You could even combine this with the current Jira priority field to have both a global priority and a project priority.
Best regards,
Peter
As others have noted, changes to the Prioirites field is global across all projects.
The best workaround I have is to create a Custom Field. Make it a single-select field (like Priority) and name it "[project] Priority" - use the name of your project. Add the priority names you want and then set an appropriate default value (or it won't show up in existing tickets). You then have to add this Custom Field to a custom Screen Scheme and associate that custom Screen Scheme with your project.
You can move the custom field to where you want it by configuring the custom Screen Scheme (configure project --> Fields --> click on the Screen Scheme in question). You can drag and drop it to where you want it to go.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Whip,
you can also try Extended Schemes for JIRA. It allows to configure individual list of priorities for Project & Issue Type pair. It also provides individual configurations for Resolution and Link Types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian is planning on making Project specific priorities available sometime: https://jira.atlassian.com/browse/JRA-3821
There's a couple different workarounds that you could try:
1. Add all possible priorities to the priority field. Then add some javascript to your announcement banner to hide all priorities which are not valid for the issue the user is currently viewing.
2. Create a separate priority select list custom field for each project. Then create a listener which will update Jira's Priority field with the value in your custom field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JRA-3821 has been implemented as of version 7.6.0.Server
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As of September 2017, Atlassian has said this suggestion is being planned for an upcoming release. (see https://jira.atlassian.com/browse/JRA-3821)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I use workflow post functions to do this, works fine for my use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Priorities per Project and Resolutions per Issue Type is an issue from long back. you can check https://jira.atlassian.com/browse/JRA-3821 and vote for the issue.
Also some work-arounds are mentioned on velocity files of priority and resolutions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can try to use: https://marketplace.atlassian.com/plugins/ru.mail.jira.plugins.uniqueregexfield
This Add-On provides unique value fields by JQL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.