Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

When a version is released, how do you update the status of linked tickets from another project

Dom July 8, 2022

When a new version is released in one of my projects, I would like an automated action that finds the tickets from that fix version that are linked to tickets from another project and update their status.

Pseudocode of what I'm trying to do:

  • When: Version released
  • Project equals "Project 1 (P1)"
  • For issues in fixed version
    • For linked issues
      • Project equals "Project 2 (P2)"
      • Then: Transition the issue to "New Status"

I can't find a way to add a loop within a loop ("For linked issues" inside "For issues in fixed version").

I also tried making the release update a custom field that would then trigger another rule to update the status of linked tickets but couldn't figure out how to use the custom field update as a trigger either.

Is there any/another way of doing this?

2 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 8, 2022

Hi @Dom 

With an automation rule, you cannot nest branches/loops currently. 

What you can do is divide and conquer to solve the problem with 2 rules:

  1. use your rule, up to the point and including the first loop, and add a value/comment/etc. to delegate to those issues
  2. create a second rule, triggered on the condition from step 2 and with the option enabled to "Allow Rule Trigger".  This second rule will walk the linked issues and perform the transition, as needed.

Kind regards,
Bill

Dom July 11, 2022

Hi @Bill Sheboy 

Thanks for your suggestion. It is similar to my second attempt. I got it working by creating a very specific comment that then acts as a trigger to the second rule.

Best,

Dominic

Like Bill Sheboy likes this
0 votes
Jack Brickey
Community Champion
July 8, 2022

have you tried the 'Lookup issues" action?

Dom July 11, 2022

Hi Jack,


It could work, but since "Lookup issues" has an upper limit of 100 issues, it may result in unexpected results.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 11, 2022

Hi, Dom.

As an FYI...everything in automation rules has the 100 issue limit: triggers with JQL, branches, and Lookup Issues.  One work-around is to chip-away at a problem, 100 issues at a time, by marking issues so that they are not picked up by subsequent rule executions.  e.g. by adding a flag/value so they no longer match a JQL statement, and allowing the rule to run repeatedly.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events