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
I have few issues when it is was moved to the final state "Released" Resolution is not updated as Resolved and it has still been in Resolution: Unresolved which is not correct also this was impacting the "Average age chart" used in the Jira dashboard as it looks for the Resolved state to create a graph.
Later the workflow is updated with the post function to update the resolution as resolved for final state 'Released'. Further which the resolution is updated as expected for newly created issues. But it is not getting updated to the existing issues in the final state.
Can we achieve this for existing issues also by anyways?? Please provide your inputs or guidance.
Hi @Dave Mathijs ,
Thank you for your quick response.
I was considering the workaround on re-transit the issues back or doing bulk update, but I am afraid that "The Average Age" chart will be impacted.
I may try using the Script Runner plugin to see if I can update only the resolution field without making any changes in status transition.
The resolution date will indeed be set once the resolution is not, not upon the date/time of the status change. This will indeed impact the Average Age chart.
Charts, KPIs and SLAs are useful, more important is to understand them and being able to explain them.
If you can explain WHY the average for a certain period is higher (because of this correction), I'm sure people will understand.