You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Atlassian Community!
Looking for any alternative ways to solve this problem we have with an automation.
We were previously on Jira premium plan but downgraded to standard. With standard + our JSM standard we get a total of 1000 multi-project / global automation executions regardless of whether those executions were successful.
We have 2 business critical automations as well as all our disaster recovery backups running, and we are always over this 1000 executions.
Because the automation rule starts at the top with the trigger which you cannot filter as far as I'm aware -- my trigger is when an issue transitions to particular statuses. The problem is: I only care about issues in certain projects and not across all of Jira. The trigger unfortunately looks at every project and every issue transitioning to my specified statuses. We have a LOT of projects and issues which means this automation rule runs all the time.
I have worked with Atlassian Support several times to figure out how to optimize this rule. It focuses on issues linked from a single project to another 13.
In a nutshell the rule is looking at:
OTHER THINGS I'VE TRIED
I have also looked at workflow transition actions like conditions, post functions, etc. It doesn't look like any of them will do the trick.
Any feedback you can provide would be really appreciated. Thanks so much!
If you are the Jira admin you can create global automation and select the scope for multiple projects as necessary without having it run through all projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.