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
Next: Root
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.
Has anyone recently notice inconsistency whereby a Jira ID has a workflow in "DONE" status but the Resolutions is on "Unresolved"
This falls within Workflow & Transitions but am curious to know what causes this inconsistency.
I have experienced this same issue. To resolve I have added post functions on the transition that update the resolution status automatically. Let me know if this is an approach you'd like to take and I'd be happy to share details about how to add those postfunctions to your workflows.
Hi,
Kindly check if 'Done' transition has post-function to set the resolution value. If there is no post-function, then it is an expected behavior. May be your workflow could have been recently modified.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Walter,
Was the ticket transitioned from "Done" back to another preceding status?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I reviewed the activities and it seem it was first from To Do to Done, then later reopened to InProgress then DONE. Its my assumption the team was trying to see if the Unresolved resolution will re adjust in vain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a common reason; if the ticket moved from a resolved status to a previous status, the value of the resolution field automatically sets to "Unresolved".
To resolve it, your Jira Admin will need to update the workflow setting (backend automation I suppose) to:
Hope this helps.
:)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.