There's several of ways to do it. Both of the main ones rely on you identifying at what point in the lifecycle you want an issue to become "resolved" and looking at the workflow transition that should be taking them from unresolved to resolved (transitions change the status, so I usually recommend people get the list of status in the workflow and divide them into two piles - one where an issue needs more work, and done/resolved/ended/etc. Then look at all the transitions going from one pile to another, as that's where we need to think about it)
First, there's the interactive way - for transtions going from unresolved to resolved, add a "screen" to the transition. Make sure the screen includes the resolution field. Users will then set it during the transition.
Second is the non-interactive way. Same set of transitions, but you add a post-function for "set resolution field to fixed".
Third, you also need to pick up the "reopen" transitions. On them, you use a similar post-function, but "set resolution field to <none>"
You can see the first and third point in the JIRA default workflow, as an example.
There are other ways to change resolution (if you have JIRA Software, there's a flag on the status in the workflow. Or listeners. Or other bits of code. Etc).
Edit the workflow and click on the transition that go to the status Done. On the menu on the right side, click Screen, and select Resolve issue screen. From that moment on, changing the status to Done will prompt a dialog window to enter the Resolution.
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG