Automation: change status of related support tickets when version is released

[Elmer A]

When a version is released, I want the issues that are related to the issues that were part of the release to change status.

So: Version Released > Lookup all issues in that version > Lookup all related (support) issues > Change status of those support issues

I have come this far but as you can see it gives an error and I have no idea how to change this to get it working. Hope you can help.

[Bill Sheboy]

Hi @Elmer A 

That error indicates there is no issue available at that point in the rule for the branch.  The reason is the trigger is on a Version and the Lookup Issues provides data and not issues.

When you want to iterate over the issues in the Version, use that branch type: Issues Fixed In Version.  

However you seem to want something slightly different:

GIVEN a Version exists with issues assigned to it by the Fix Versions field
AND those issues have linked issues
AND the linked issues are in project CSUP
WHEN the Version is released
THEN FOR EACH of the linked issues...
    Add a comment to the issue
    AND transition the issue to Ready for Validation

Your rule could use the Lookup Issues action to first find the issues in the Version (as you have done), and then use a JQL branch to iterate over them:

• trigger: version released
• action: lookup issues for the issues in the version
• smart values condition: to confirm there were results found
  • first value: {{lookupIssues.size}}
  • condition: greater than
  • second value: 0
• branch: on dynamically-generated JQL to get the linked issues

project = CSUP
  AND status NOT IN ("Ready for Validation")
  AND (
        {{#lookupIssues}}
          issue IN linkedIssues("{{key}}") {{^last}} OR {{/}}
        {{/}}
      )

• action: add the comment
• action: transition the issue

Please update that JQL to meet your needs, perhaps adding additional checks on the Status value or the link type.

Also note: this rule is updating issues in a different project, and so it will need multiple-project scope (in the details at the top of the rule).  Please ask your Jira Site Admin for help making that change using the global automation permissions.

Kind regards,
Bill