Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Single Project scoped Rules not working, only Global Rules

David Loszewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2020

Hello,

I was wondering if someone could enlighten me on the use of Global vs local rules?  I have had no luck getting any of my single project scoped rules to work, but when I recreate them as a global rule they work as expected.  Currently, when I create a rule with a single project scope, the rule runs but does not match on anything.   

For example:

automation.png

Screenshot_20200303_203036.pngIf I run the same rule as Global, it works fine.   Obviously the problem that I'm facing currently with running everything as global is that when an issue is created, its' currently running through about 7 different rules right now.

Any help would be appreciated. Thanks!

1 answer

0 votes
John McKiernan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 3, 2020

Hey @David Loszewski 

I may be able to help here.  

Looking at the screenshot of your rule above, it looks like your JQL branch is working off a different project(s). Because of this, it won't work as a single-project rule. 

The best option for you here would be to run a multi-project rule where you can specify which projects you want it to run across. In your case, it would be Asset Tracking, Customers, Customer Numbers. 

A global rule, as you would expect, runs across all of your projects. This is ideal when you want to create one rule that has the power to act across every part of your Jira instance. In this case, it is probably too much oomph! 

Automation rules - Jira 2020-03-04 13-08-34.png

 

When you say: "Its' currently running through about 7 different rules right now." - can you clarify a little further? Do you mean that other rules are being triggered by this one?

Thanks,

John

David Loszewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2020

Thank you John, I'll have to try running it across projects.  For you questions regarding the multiple runs, I think it's because they were triggering on "when ticket is created" but since they were running globally, they would all kick off when a ticket was created in any project.  

My goal is to have it run only if the ticket is created in project AT, the JQL query is because I'm comparing trying to compare the info in the created ticket against info in other projects which I will be linking to.  

John McKiernan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 3, 2020

Hey David, 

it should only run for when a project is created in AT (from looking at your rule). 

By adding that condition in there, you have ensure that it won't run every time an issue is created (which could obviously cause havoc!) 

Do you have any other rules that might be causing it? May be worthwhile to put the ticket through to support if you can't troubleshoot it :)

Cheers,

John

Suggest an answer

Log in or Sign up to answer