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.
Context: For JSD issues with no resolution or resolved date, we retroactively bulk added the resolution date and resolution state.
Current Issue: When the resolution date was retroactively set the SLAs were updated to the date updated instead of the actual resolution date. The resolution date is correctly set to a past date according to the status category change date.
Open Question: How can we trigger SLAs to be accurate to the retroactively set resolution date?
This seems like poor practice that assignees aren't setting the resolution status when they actually resolve the ticket.
Regardless, If the status category change date that you mention is the actual resolution date, then this should be the Condition for "Finish counting time when..."
Suzi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.