I have designed workflow based on some 4-5 states, like open, Resolved, Reopen, Reject and Closed and I want to use the same as a resolution field. I am not letting user to enter the resolution field.
I used update field functionality of the workflow to update the resolution field based on state transition and the same is used(I guess) to decide whether issue is resolved or not(In reports and other Issue screens).
So when the issues are reopen I want the resolution to be Unresolved. I tried keeping it none but it didn't workout.
Please suggest some solution.
As it looks like, you are using or you would like to use your own workflow, with
two "add resolution" transitions (Resolved, Rejected)
one "clear resolution" transition (Reopen)
one "accept resolution) transition (Closed)
For the steps "Resolved, Rejected" you need as post function the edit issue field resolution and then select the corresponding resolution. The process will be, that after the transitition the issue field resolution will automatically be set to the selected resolution.
For the "Resolved" transition you need a "Resolved" resolution, normally not there in Jira out-of-the-box.
For the "Rejected" transition you need a "Rejected" resolution, normally not there in Jira out-of-the-box.
For the transition "Reopen" you need as post function the edit issue field "Resolution" and field value "None". The process will be, that after the transitition of the issue Then the Resolution of the issue will be cleared. A "cleared" resolution is an unresolved resolution. This is handled automatically by Jira.
If you are not allowing users to select a resolution manually, you should remove the Resolution field from the transition screens, if you are using a transition view.
I hope, this answer was helpful and not too long.
You need a post function to clear the resoluution when you use the "reopen" transition. Use the "update field" post-function that is built in - it should display "Clear the resolution", not "set it to none"
Have a look at the default built-in workflow that you cannot edit, that uses it on re-open, so it's a good example.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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