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
Agreed but common in our instance since there hasn't been an admin to set standards!
Now we're cleaning it up and finding gaps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.