Automation Rule Details Scope Options

[MA]

Hi All,

Currently the scope options for Automation Rules in Jira is:

• Single Project
• Multiple Projects
• Project Type
• All Projects

If you have multiple rules that you want to run for a subset of projects then these options don't really work well.

Currently I use Multiple Projects and add the project to every rule every time we create a project in our team, but this is a pain.

Single project obviously won't work.  I don't want the rules applied to all projects and project type is too coarse in granularity and doesn't map directly to the relevant subset of projects that I want to use.

What will work is using project category, as I can set up a project category and use this category for my set of projects.  Unfortunately, project category is not available when setting the scope option for automation rules.

So my questions:

1. Are there any plans to add project category as a scope option for automation rules?
2. Apart from my current approach or setting all my rules to run for all project and then having conditional processing against the project category smart value (not very efficient and will chew through the rules execution count), can anyone suggest a better way for running a set of rules against a set of projects?

Thanks in advance

MA

[Jack Brickey · Accepted solution]

This is a useful suggestion. You might wish to use the in-app feedback link to share your thoughts with Atlassian. This forum isn’t the best means of connecting with the Atlassian product owners.

[Bill Sheboy]

Hi @MA 

Yes, and...to what @Jack Brickey notes: here are the suggestions to add that feature for category scoping: 

• https://codebarrel.atlassian.net/browse/AUT-805
• https://jira.atlassian.com/browse/JRACLOUD-76420

For work-arounds...

• What you describe with a category condition test using all projects scope seems like a good approach.  Obviously this option isn't viable for customers who do not have the execution volume of Premium licensing.
• For your rules scheduled triggered on JQL, you could investigate using entity properties to check an prevent the rule triggering

Best regards,
Bill

[MA]

Thanks @Jack Brickey & @Bill Sheboy .  I have added my experiences to the Jira issue you advised in your post.  Hopefully the suggestion/request will gain traction with Atlassian in the near future.

[Margo]

I have similar problem with automation fired on events, especially issue created event. As my projects use all the same workflows, I'm going to change event to custom and start rule with this event instead of issue created. I'm testing this approach.