Bug Resolution

[Karen Thomas]

I'm new to Jira and am configuring a project for my teams.  With the release of the new view our "resolution" field was hidden. I understand now why since it's critical to reporting in Jira. I'm following the documentation to add it to our workflow in the "Done" step.  I'm wondering, though, what impact the different resolution statuses have on the different reporting? We would use the status primarily for Bug Resolutions and not for Stories. So should I just create another custom field for Bugs that our QA team could use so they can easily track bug status? The other consideration is that there are other teams who have been using Jira so want to tread lightly. 

[Joe Pitt · Accepted solution]

The value of the field can be used in reporting, but has no impact on whether an issue is resolved or not. Any value other than the initial 'unresolved' means the issue is resolve. 

Resolution Field

Resolution Field can't be made optional. DO NOT put the field on any screen except the one presented in the transition where it is to be set. Resolution is a special field in JIRA. It has an initial value of ‘Unresolved’, which means the field is NULL in the database. It is ALWAYS required when it appears on the screen. ONLY display it on the screen during a transition to the status where you want it set. Once it is set the issue ID will appear with as strikethrough. If you re-open an issue the transition from closed to reopen needs to have a post function to CLEAR the resolution field to set it back to Unresolved.

[Nidhi Sachin Jindal]

Hello,

Just wanted to check about the Bug Lifecycle process in Jira Cloud, is it possible to change this cycle in Jira? Please suggest.

Regards

Nidhi