Automation Rule - Not Triggering based on Linked Issues

[Stephen Call]

Hello!

We have an automation rule that is configured to trigger when a Request moving to the 'Waiting on IS for Info Sec Review' status

With this automation rule, we have a conditional that looks for any linked issues that have "- InfoSec Review" in the summary, but we are finding that there are situations where the conditional is being met, but there are no linked issues with the - InfoSec Review in the summary. 

Any additional guidance on where to look at why this automation rule isn't creating the 'Task' would be greatly appreciated!

Thank you!

Stephen

[John Funk]

Hi Stephen,

I would add a Branch for Linked Issues and move those other actions under it. You will need to change the Link Issue action to be based on Trigger issue instead of Most recently created issue. 

[Bill Sheboy]

Hi @Stephen Call 

First: are all of the issues you are checking in the same Jira Project?  If not, the rule scope will need to change from single-project to multiple-project or global.  Your Jira Site Admin will need to help make that change.

If that does not help...I have observed the Related Issues Condition with JQL producing unexpected results, particularly with the "None match..." option.  I recommend using the Lookup Issues action instead and then using the Smart Values Condition to explicitly test your results.

And, you seem to want to test the phrase "InfoSec Review", and so please use the exact phrase syntax with your JQL and the CONTAINS ~ operator.  Finally, the dash - in your JQL likely has no impact (and probably cannot be searched for with built-in functions).

Putting that all together, the condition could be replaced with these two rule steps:

• action: Lookup Issues
  • issue IN linkedIssues("{{triggerIssue.key}}") AND summary ~ "\"InfoSec Review\""
• smart values condition:
  • first value: {{lookupIssues.size}}
  • condition: equals
  • second value: 0

Kind regards,
Bill

[Joseph Chung Yin]

@Stephen Call 

I agreed with @John Funk suggested.  I assumed that you have also tested out your JQL where the issuekey doesn't show up the in the resultset?

Kindly advise.

Best, Joseph Chung Yin