How to automate issue transitions in Jira?

[Shilsha Technologies]

I’m looking for a way to automatically transition Jira issues when certain conditions are met, such as a field update or a status change. What options are available using Jira automation or workflows to achieve this? Any best practices or common limitations to consider would be helpful.

[Trudy Claspill]

Hello @Shilsha Technologies 

Welcome to the Atlassian community.

What subscription plan is being used? The number of Automation Rules that can execute in a month can be limited by the subscription plan.

Are you familiar with Automation Rules? If not, click on the Learning link at the top of the Community pages and take advantage of the free, on-demand courses concerning the topic. Here is a basic search to help you get started:

https://community.atlassian.com/learning/catalog?product=Jira&search=automation

There are also Templates available for rules which you can use as a starting point for a new rule.

With Automation Rules you have multiple rule triggers available, include Work Item Transitioned and Field Value Changed. You can add Condition steps to the rule the further constrain when the rule should proceed with execution. And there is an Action to Transition Work Item . You can find the full documentation set here:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

[Andrea Tagliabue]

Hi @Shilsha Technologies 

automation is the most flexible and recommended approach for automatically transitioning issues based on events and conditions especially in Jira Cloud.

Here is a practical example:

@Trudy Claspill gives you all the information about automation, so I can just add an interesting option for workflow work items: the ability to make a global transition available only via API requests, which in our scenario is triggered by automation.

Here is an example:

This way, you can keep a transition hidden but still make it available in specific cases.

Finally, if you have subscribed a premium JSM instance, all the features mentioned above are also applicable to Journey and Playbook, exponentially extending the customization possibilities.

Playbooks (step‑by‑step guides and automation in work items)

Journeys (end‑to‑end connected work item processes)

Ciao