How to Automate Issue Transitions in Jira Using Automation Rules?

[Malik Hassan]

Hi everyone,

I’m working on streamlining our workflow in Jira and looking for the best ways to automate issue transitions. Specifically, I’d like to:

• Move an issue to "In Progress" when someone starts working on it.
• Transition an issue to "Done" when all linked sub-tasks are completed.
• Send alerts when an issue is stuck in a status for too long.

I’ve explored Jira Automation but could use some guidance on setting up effective triggers, conditions, and actions. Has anyone successfully implemented similar rules? Any best practices or common pitfalls to watch out for?

Additionally, we manage Delta Executor APK, a scripting tool for Roblox, and use Jira to track updates, bug fixes, and user feedback. If anyone has experience with automation for software projects like ours, I’d love to hear your insights!

[Mikael Sandberg]

Hi @Malik Hassan,

Welcome to Atlassian Community!

For the Done transition automation, have a look under Templates in Automation, there is a rule called "When all sub-tasks are done → move parent to done" that is exactly what you are looking for.

For the first rule, how do you determine if someone starts working on the item? Do the user have to update the item or transition it?

For your third automation, create a scheduled automation that used a JQL to find issues that have been in the same status for specific amount of time. You can use the updated field to find when it was last updated and then use CHANGED to specify the statuses. Teh other option would be to use an app like time in status that can give you the specific timestamp when the status change happened. Check out this article for more information.