Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Global automation multiproject linked issues condition does not return any issues

Rosana Casilli November 3, 2022

Good morning All!!

I am trying to create a global rule to be excecuted manually from Project A and change the status based on issue from Project A in issue in Project B

 

AR.png

The problem I have is the the linked issues condition, although the JQL retrieves the issue that applies the condition, when the rule is manually excuted in the audit log show the following:

AR.png

What am I doing wrong?

 

Thank you so much for your help.

Ro

1 answer

1 accepted

0 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 3, 2022

Hi @Rosana Casilli - From what I can see, this rule will always fail.  Your trigger issue is in a status of PRODUCTTWO, but then you branch into linked issues and then add a condition that for each linked issue, its linked issues status = READY TO RELEASE AND project = CA.  Since your trigger issue is not in the CA project and status =  PRODUCTTWO, it will not satisfy the linked issue condition.

Rosana Casilli November 3, 2022

Hi Mark!! thank you for you quick answer.. 

 

So if I want to change the status of linked issues in project CA that are in Ready to Release status to Close when the issue in project TS2 is in status PRODUCTIVO, how should the rule be?

 

Thanks in advance,

Ro

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 3, 2022

You could do something like this...

Between your condition status = PRODUCTTWO and the Branch, add this:

  • LookupIssues
    • project = CA AND issue in linkedIssues({{issue}}) AND status != "Ready to release"
  • Advanced Condition
    • {{lookupIssues.size}}
      Is Greater Than
      0

Then remove the condition inside your branch

Rosana Casilli November 3, 2022

Hi Mark!! 

Thanks once again

this is how I have the rule right now after the changes, is it correct?

AR.png

If so, when I execute the rule:

ar1.png

It succeded but the advance compare condition is failing

I need that issues linked to TS from CA project in status "ready to release" to be closed.

sorry for bothering but I am struggling here... :(

 

Ro

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 3, 2022

So a few tweaks:

  • The lookup issues and subsequent condition should be BEFORE the branch.  This will make it so that it validates whether the linked issues even meet the criteria before branching through the various CA issues.
  • As I look at this again, you'll want to change a couple things:
    • The Advanced condition should actually be Less Than 1 (error on my part)
    • For the branch, I'm assuming you only want linked CA issues to be transitioned so you'll want a condition for Project = CA inside the branch
Rosana Casilli November 7, 2022

thanks a lot Mark!!! it worked perfectly!

Like Mark Segall likes this

Suggest an answer

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

Atlassian Community Events