What are Best Practices for Organizing Jira Automation Rules?

[Justin Heidema]

I am looking for ways to manage and organize our organization's Jira Automations effectively.

We are presently working with 16 pages of automation rules. Keeping up with this many rules and comprehending their individual impacts on our Jira workflows has proven to be increasingly challenging.

We have incorporated labels into our organization's strategy, but are curious to know if there are other mechanisms that could be employed to better structure our rules. Are there any marketplace offerings that might help us in this regard? Additionally, are there any new features or changes anticipated in Jira's roadmap that could aid in our organization's efforts?

Thank you.

[Aron Gombas _Midori_]

Interesting timing that this question came up just today. There was a related article published yesterday:

https://community.atlassian.com/t5/Jira-Cloud-Admins-discussions/Efficient-Jira-Automation-A-Governance-Approach/td-p/2431430#U2431509

I also understand your problem/frustration and I think that the right way to handle this would be using "automation rule sets" (my idea). But, I think right now, there is nothing better than using labels and maybe rule name prefixes/suffixes.