You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm facing one issue, when i put the final status -UAT Ready or Closed which in done status by default, i get resolution filed near to status with tick mark , and when i am trying to roll back to any other status , this tick mark with resolution always showing with all status which i don't need, I need to only resolution for closed /UAT ready status,
also i see few of status automatically showing strike on ticket for other statuses like 'Awaiting testing' and ' In Testing' which i also don't want
Please help me on it
Thanks Ravi for prompt response, i am not seeing checkbox field in column mapping , may be its not in JIRA cloud,
When you resolve an issue, the resolution field is update with any resolution value. This means, the issue was resolved. And you want to go back, examples Done to Open, you need to clear the resolution field with post function or automation. If you don't, even issue is in Open, it appears like its resolved.
Please check and update your post function includes resolution updating.
Thanks Burak, yes it works, you have resolved my big headache :-)
The resolution and status are totally independent of each other in the code, it is up to your admins to determine how they work best together for your process.
The strike-through happens when the resolution is set.
You set the resolution by having it on a create, edit, or transition screen (hint - never put is on create or edit - you don't want new issues to be created as already resolved, nor have simple edits set the resolution). Or you can set it in a post-function on the workflow when moving it from one status to another.
You can also clear it out with post-functions.
My guesses are:
that your workflow does not clear the resolution when re-opening your issues.
that someone has a resolution field on a create or edit screen for the awaiting or testing
(You can also set and clear it with automation or listeners, but these are clumsy because they run outside the workflow, and the workflow is the best place to do it, because it's the thing determining the route through the process)
Thanks Nic, Yes after setting resolution field 'None' it cleared when i rolled back