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 · Accepted solution]

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

[Elmer A]

@Bill Sheboy Wow, this works! This is fantastic. Thanks so much for your help!

[Diego Arturo Bustos Aponte]

@Bill Sheboy  Hello, if I want to scale it up so that it is global, I would not want another project that also has issues in the initial state to change when the action is executed. It should only take those from your project. What do you suggest would be best in this case?

[Bill Sheboy]

Hi @Diego Arturo Bustos Aponte 

As this is a very old, resolved thread, I recommend creating a new question with the "Ask a question" button at the top of the page, and perhaps add a link to this thread for context.

When creating your question, please remember to post images of your complete rule, the audit log details, and explain what is not working as expected.  Thanks!

Kind regards,
Bill

[kh-federico]

Hi @Diego Arturo Bustos Aponte 

This topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.

Thanks!