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
hi all Jira administrators,
I have a workflow that expect a Done status, once a Resolved one is received.
the primary goal of that, is to expect the reporter taking an action when he receive a resolved status on Jira, to test and confirm the raised issue is properly corrected.
When it is, he must transition its Jira to Done.
An automation should solve this but from my point of view, it means the reporter do not care about testing the Jira. (He may did it but did not confirmed that to assignee)
What's your suggestion in your company?
thanks for sharing your advices
Hi @Carolina SILVA ,
that is a usual problem. In my company we use a post function on resolve transition that automatically assign ticket to reporter for confirmation.
In order to avoid that a ticket remains in a resolved status, we have put in place an automation that automatically move tickets resolved after a 2 weeks based on last update date.