Automation avoid duplicates during loop creation

[Olga Videc]

Hello, 

I have an specific case of automation.

1. When a version is released i what to check all the story's/tasks that are part of that fix version.

2. Each story/task has a field called System it's a asset filed and what I want to do is create a separate change request in another project for each of those systems.

The tricky part is some story's have a same system (the value is the same) so no need for duplicate issues.  The trick is to catch and compare the issues that are created during this automation the issue is that the create branch in this automation is a separate branch and i cant check them.

Has anyone had similar issue?

BR, Olga 

[Bill Sheboy]

Hi @Olga Videc 

Does your rule do / check anything else with the issues found in the released version?

If not, perhaps consider this approach using a lookup to find the distinct System values:

• remove the branch on issues in version
• use the Lookup Issues action with JQL to gather the issues
• use the distinct list function to identify the unique values
• use an Advanced Branch to iterate over those to add one change request for each

One possible challenge with this approach is asset values can have delays looking up their data, so I recommend testing with practice rule which only writes to the audit log.  For example:

• trigger: manual
• action: lookup issues with JQL to gather issues for an example Fix Version value
• smart values condition: to confirm results were found
  • first value: {{lookupIssues.size}
  • condition: greater than
  • second value: 0
• log: to write the distinct values for the System field

distinct System values: {{lookupIssues.System.distinct}}

Kind regards,
Bill