Stop rule triggering if certain condition is met.

[Chris.Buckley]

I've got a rule where an epic is created if a component is selected. 

There are 6 components that should trigger this rule. However i only want 1 epic to be created if multiple components are added. E.g. If 3 components are added, i only want 1 epic to be created.

I've found that when i added 2 components at the same time, only one epic was created. However when i added a 3rd component afterwards, a 2nd epic was created.

How can i build a rule that checks if an epic has been created, the automation doesnt trigger?

[Marc - Devoteam]

Hi @Chris.Buckley 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

[Marc - Devoteam]

A rule can only not execute if a condition is not met.

If a condition is met the actions will execute.

Based on you requirements, my suggestion os to create multiple rules, instead of trying to accomplish this in a single rule?

[Chris.Buckley]

If i create individual rules, the problem remains the same, i end up with multiple epics when i only need one epic regardless of how many components are selected.

[Marc - Devoteam]

Hi @Chris.Buckley 

Please show the rules and  the configurations of the steps in the rule.

[Chris.Buckley]

[abelalia87]

Hi @Chris.Buckley ,

You can add one more condition, "Related work items condition". Then select the link type, then condition, maybe "Are not present" or "All match specified JQL". Select the condition that meets your requirement. 

The idea is you want to check if there is existing Epic linked to the initiative. 

If you want to create another EPIC for the same initative if the component are added at a later time, then you can maybe try the JQL condition and add created date in the JQL. 

If you want just one EPIC for one Initiative then the "Are not present" condition should be fine, given you have unique link type for that EPIC Initiative link.

[Marc - Devoteam]

Hi @Chris.Buckley 

You rule has issues

All clauses are OR, so no matter what the clause if the issue  component changes it will create an Epic.

So based on the trigger of the rule, if the field components is populated with a new option an Epic is created.

So you need to define when should an Epic be created?

[Chris.Buckley]

But the condition needs to be OR, if i have as AND, it will only create and epic if all are selected?

An epic should be created If one of more of these components are selected. But the epic would be for the same project, so only one epic is needed.

[Marc - Devoteam]

HI @Chris.Buckley 

See this example (values used are different, adjust the to your needs)

The JQL items not present is a Related work items condition

[abelalia87]

@Chris.Buckley 

The condition automation component "Related work items condition" should do the trick. You can create a custom link type from the Admin 'Settings' -> Work Items -> Work item linking. This should give more context on the Epic ↔ Initiative link, and wont trigger false positive if linked with other work items.   

The answer by @Marc - Devoteam is more straightforward. No need for custom link type.