How to use one Automation rule as trigger point for another

Question

Hi,

One of the checkbox I see in Rule details " Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

How do we use it or how do we use one rule as a trigger point for another?

So my problem is:

I have one JIRA project as ERFC and another 50+ projects. What I want is if Sprint field gets changed in ERFC, linked jira in ERFC get notifications. Now because link can be to any of the 50 projects, I have set it to global level.

Impact of setting this at global level is that rule starts running for all projects and this is increasing my monthly usage.

so what I want is Create rule in ERFC and it triggers Global rule only if it passes conditions. Is it possible?

Peyush Agarwal_1dgyi8 · Answer

Hi Stephen,

Thanks for your response but this wont help. Reason being that what I am trying is Script will trigger for Project A if Sprint field is changed

if Sprint field is changed any JIRA linkd with the above which can be Project 25 or Project 50 will further gets updated. Because of this I am having to change the scope of script to All Projects and which is making script for all projects.

Thinking on your suggestion, maybe I will check if we can use JQL selecting this specific project and make it Global

Stephen Sifers · Answer

Hello Peyush!

You've got an interesting idea, which we should be able to solve with automation. If I understand your basic requirements, they are as follows:

* Limit monthly usage
* Only focus on Sprint field changes
* Run against all projects

Since you're only focused on the sprint field change, you may not need other rules (or ensure this rule is above other dependencies). You'll just need a single rule that monitors (and is triggered) for that field change. This will be requirements 2 and 3.

Now, Ideally, you'll want to have a trigger based on a field change, for your example it'll be the sprint field. To do this you'll need to have a rule using the following: Automation triggers | General triggers , this will watch for the change of the sprint.

Something to note about triggers is:

The rule will run when a field value is changed. All system and custom fields are supported by this trigger.

This rule should only run when triggered allowing you to meet requirement 1 of limiting monthly usage. If there is no change to the field the rule won't be met and it will not run.

Hope this is helpful in setting up your automation rules.

Regards,
Stephen Sifers