Cloning automation rules or linking to multiple projects

[Yatish Madhav]

Hi

I think I MIGHTVE posted this before or commented but cant find it.

Is it possible to link an automation rule to multiple projects automatically or through the REST API through a connect app?

Or if a project is created and "share project settings" is selected, then it should auto-add the new project to rules setup on the original project.

Please let me know if there is a way or a workaround for this?

Thank you
Yatish

[John Funk]

Hi Yatish,

No, there is no mechanism to dynamically create automation rules. That all needs to be defined up front when you manually create the rule. 

[Yatish Madhav]

Thanks for the reply. The issue is when creating a project with sharing project settings, I would like all the rules linked to that project with the new one ... And same by associating the Projects on a rule via the API.

[John Funk]

Understood, but that is currently not available. 

[Yatish Madhav]

Yes I know :) This post is to see what is possible and to find out if there is a workaround, advanced automation, add-on or other way to try get this working ...

[John Funk]

:-)   The work around would be what @bmccoy  mentions below. Export the rules and then import under the new project. 

[Mark Segall]

Hi @Yatish Madhav 

The best way to handle this type of scenario is to make the rule global and leverage a condition based upon project category to enforce whether the rule executes or not.  

[Yatish Madhav]

Thanks @Mark Segall  Thanks, I have thought of that too ... But in an instance currently with around 900 projects, it may be tricky on how to condition it. I was really hoping not to go the global rule route :)

[Mark Segall]

Unfortunately, there's really no other way around it with the available scopes as Single/Multiple project and global. I'd love to see them add Project Category as a scope option.  It would solve a lot of noise on global rules.

[Yatish Madhav]

Oh yes, that would be super! I will keep searching until this is available hehe

Thanks for the reply. 

[Bill Sheboy]

HI @Yatish Madhav 

Yes, and...to Mark's ideas about using a global/multiple-project scope rule:

You appear to be on a Standard Jira cloud license.  Is that correct?  If so, there is a limit of 500 executions per month with global/multiple-project scope rules for Standard license.  If you expect that you will need more consider either using some project rules to reduce the usage or investigate options to upgrade your license level.

Kind regards,
Bill

[Yatish Madhav]

Thanks @Bill Sheboy - yes thats correct. Yeah, I am aware of those limits but that is a caveat and not a show-stopper, Id say. All I would prefer is if there is a way to automatically link/associate rules when share settings is selected so there is true project settings sharing :) 

If Atlassian doesnt provide this or if there is no workaround, I guess the best route is either manual project linking OR global rules with conditions as above OR manual rule per projects - all of which have their pros and cons.

[bmccoy]

Hi!

I know this isn't solving the fundamental problem you'd like fixed.  But, I have seen other customers have a set of rules that they have exported.  Then for each new project, they import those rules into the project. 

It might just speed up that manual rule option.

Cheers,
Brydie