How to Automate Issue Transitions in Jira Using Automation Rules?

Question

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!

Drew J Goldfarb · Answer

For a project that involves frequent game file  updates, bug reports, and user feedback, Jira Automation can make the workflow much easier to manage. For example, you could use issue-created triggers for new reports, conditions based on labels or priority, and transition rules when development or testing is completed. For “Done” transitions, I’d also recommend checking that all required subtasks are actually resolved rather than relying only on the parent issue status. We use a similar issue-tracking approach for keeping game-related files and updates organized, and clear labels/version numbers make it much easier to connect reported bugs with the correct release.

Zoya Khan_s187ti · Answer

Automating issue transitions in Jira can help streamline your workflow and reduce manual steps. To move an issue to “In Progress” when work starts, you can use the “Issue Assigned” or “Issue Updated” trigger with a condition to check the current status. To mark an issue as “Done” when all sub-tasks are completed, use the “Sub-task Resolved” trigger with the “All Sub-tasks Completed” condition. For alerts on issues stuck too long, a scheduled trigger with a JQL filter works well to send reminders or auto-transition them. Start with simple rules and build up gradually to avoid conflicts.

Mikael Sandberg · Answer

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.