Jira Automation - Duplicate Child Issues

[Pablo Gomez]

Hi there.

I am working on creating an automation rule that when an Epic transitions to the In Review status, issues in different projects are created. I'm trying to prevent duplicate child issues from being created in the event someone switches the status back to In Review after the child issues were created on the initial run. The goal is to prevent duplicate issues being created after the rule is first ran.

Here is the rule I have setup now

I have set an IF condition to "If Children not present" but the rule continues when there are children present in the Epic causing duplicate entries. Am I missing something here?

[Katherine Chan]

I have the same issue.  The Related issue condition works for "Sub-tasks" but not for "Children".  This looks like a bug.  We try to limit custom fields so the workaround suggested would not work for us.  

[Katherine Chan]

The solution that worked for me is using "Linked Issue" condition with Link Type "Is a parent of" "are not present".

[Joseph Chung Yin]

@Pablo Gomez -

Here is a solution for you consider:

• Creating a custom field (Number format) where you will populate it to 1 when your Epic issue moves into the Review status initially.  You can then reference this field in your automation rule to determine if the field is 1, then don't execute the child issues creation, otherwise execute.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.