When release a version, update the US which are LINKED to the US in this version.

[Deleted user]

I want to create the following rule:

1. WHEN version released
2. FOR issues fixed in version
   
   1. IF linked "feature request" issue is present
   2. FOR "feature request" linked issues
      1. THEN Transition issue.

It seems I am not able to create a FOR in another FOR.

Any ideas?

[Bill Sheboy · Accepted solution]

Hi @[deleted] 

You are correct that you cannot nest branch statements to do what you ask for a 3-level branch: version issues, links to "feature request" issues, and then linked issues to the feature request.

As alternatives, have you considered setting the fixVersion of the "feature request" issues as they are linked to issues in the release?  That would make your rule simple to just check for any issues in the release to transition them.

If that will not work, you can probably approximate the nested queries using Create Variable, to dynamically build the query in multiple steps:

• Trigger: version released
• Action: lookup issues with JQL for issues in the release
• Action: create a variable to build a CSV list of the Keys from the lookup
• Action: lookup issues with JQL for "feature request" issues which have links to the issues in the CSV list
• Action: create another variable to build a CSV list of the Keys from the lookup
• Branch: on JQL for linked issues to the keys in the new CSV list
  • Condition: if issue not in the destination status
  • Action: transition to the new status

Best regards,

Bill

[Deleted user]

I've created it!

Now we wait until we do a new release..

Thanks for the help anyways! Amazing! :D