Automation Rule scope

[Tristan Silverio]

Can one automation rule be configured to execute against several projects (not global). Background: 

I have an Integration Testing Project which has integration testing stories. These stories are dependent on stories from other projects to be Done before the integration test story can be progressed to Ready to Test. 

For example, 

Integration Story 1 is linked to Dev A story from project A (link type is tests)

Integration Story 1 is linked to Dev B story from project B (link type is tests)

I run an automation rule that scans all linked stories with link type tests and checks if status is done. If the status of all linked stories is Done then I transition the integration story to "Ready for Test" 

Problem is that Automation scope is restricted to current project so is unable to scan the stories from project A and B. I want to configure the automation scope to include stories from Project A and B as well without having to set the automation rule as global. 

[James Chan]

Hi @Tristan Silverio , 

I was running a similar problem as you do and I found out that from https://community.atlassian.com/t5/Jira-Software-questions/Automation-Rule-Scoping-Question/qaq-p/1443191 it explained that I need to be a JIRA Admin in order to run a "cross-project" rule.

i.e. setting up the automation rule "scope" to multiple projects not within a single project.

Hope this helps. 

[Bill Sheboy]

Hi @Tristan Silverio 

No, you would need a global (or multi-project) rule.  You appear to be on the Premium version, so you have 1000 global executions per month, I believe.

However... There are no such scope limitations using the web request action to access the REST API.  So if you could find the issues in a different project to change (via your links) you could update them using the REST API.  Please see this article on that approach:

https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Best regards,

Bill