If tickets are moving back from a closed / resolved status, it is because your workflows allow them to. I suppose tickets are not automagically moving back, but because either users or an automation rule is causing that to happen.
You'll have some digging to do into your configurations, most likely:
If you are using team managed projects and your workflows look like this:
the arrows from any status to all statuses of the process indicate that any ticket can be moved to any status at all time. By selecting a status and on the right side removing the check box next to Allow issues in any status to this one, you can remove that setting where necessary.
Obviously, you have to ensure that you create new transitions to allow to move tickets between the desired statuses. By dragging arrows between statuses, you can convert the above workflow pretty quickly into something like this:
This leads to much more control over allowed transitions.
To edit workflows in a team managed project, navigate to project settings > issue types and click edit workflow. You may need to repeat the process for every single issue type in your project.
For company managed projects, workflows are possibly shared across different projects and they have more configuration options. But the core principles about these transitions are similar.
Hope this helps!
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events