Any alternatives to a really complex automation rule that executes all the time?

[Gail]

Hi Atlassian Community!

Looking for any alternative ways to solve this problem we have with an automation.

BACKGROUND

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.   

PROBLEM

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.

RULE  

In a nutshell the rule is looking at:

• bug issues in Project A that are linked using a specific link type across another 13 projects.   These are considered our parent/source/original issue.
• When these issues are found, we close Project A's child/duplicate issue
• We update Project A's resolution value to match the parent issue's resolution value
• We make custom comments based on the resolution value

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!

[Najm Polaris · Accepted solution]

Hi @Gail

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.