I would like to change 2 things related to a Jira issue: 1) add Severity 2) change workflow

Question

The current issue Priority field is actually "Severity". Priority would be High, Med, Low.

I would like to change the current Priority field values to be numeric values or High, Medium, Low. Add a new field "Severity" with the values currently under Priority.  The current Priority field values in Jira make no sense for a software bug.

The Workflow of a software bug should be something like: "Unconfirmed" or "New" or current Backlog works. Then it gets "Assigned" to a person. When a developer fixes it becomes "Resolved" . Tester can "Reopen" if not satisfied or change to "Verified".  Then the bug gets "Closed". The "Closed" bug can also be "Reopened" and assigned to a developer to be "Resolved" etc.

Possible Resolutions: FIXED, DUPLICATE, WONTFIX, CANT REPRODUCE, INVALID

Can someone please guide me to make these changes? Thanks in advance!!!

Nic Brough -Adaptavist- · Answer

It's up to your administrators to change priority options, not Atlassian support.

I'd also caution you not to mix up priority with severity in the real world, they mean very different things.  Just because an issue is more severe than another one does not mean it automatically has a higher priority.  (One of the reasons Jira was written was to allow the removal of Severity from bug tracking, as it's often confused with priority and usually set completely wrong by the people creating issues)

Lanka van Dort · Answer

Thanks for the speedy reply! Will give it a try.

Anyway Jira support can change the current Priority dropdown values?

Taranjeet Singh · Answer

@Lanka van Dort  1. You can add a new drop down custom field "Severity" in JIRA with required values and then add this field to the screens used for "Create, Edit, and View" operations (recommended to create separate screens for issue type "bug" if not already created) for your issue type "Bug".

Refer this JIRA documentation on how to create screens, screen schemes, and issue type screen schemes:

https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html

https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html

https://confluence.atlassian.com/adminjiraserver/associating-screen-and-issue-operation-mappings-with-an-issue-type-938847305.html

2. If you are using JIRA 7.6 or above, you can use Priority Schemes feature to define a custom Priority scheme for your project. Please see this documentation: https://confluence.atlassian.com/adminjiraserver/associating-priorities-with-projects-939514001.html

3. You can also define a custom workflow (with custom statuses and transitions) in JIRA and link that to "Bug" issue type in your project via workflow schemes.

Please see this documentation:

https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html

https://confluence.atlassian.com/adminjiraserver0713/managing-your-workflows-964983694.html