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

Automation rule for two issues that are linked via another issue

Konrad
Contributor
August 20, 2024

 

 

 

 

 

I have two projects A and B. Issue A1 is linked to two issues B1 and B2. Is it possible to design automation rule via branching or otherwise, so when B1 transitions to ‘Accepted’ status the issue B2 transitions automatically to ‘Rejected’ status. I imagine that there is a link between B1 an B2 via A1 issue, but perhaps I am mistaken?

4 answers

2 accepted

2 votes
Answer accepted
Shikha Verma
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.
August 20, 2024

Hi @Marc - Devoteam you can achieve this by using a Unique Identifier. 

  • Create a custom field (e.g., "Unique Identifier") in Project B.
  • When linking issues B1 and B2 to A1, ensure that each issue in Project B has a unique identifier in this custom field.
    Then Modify the Automation Rule: Add a JQL condition like project = B AND "Unique Identifier" = "Value1" to target B1 and a separate condition for B2 with "Unique Identifier" = "Value2".

 

Marc - Devoteam
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.
August 20, 2024

Hi @Shikha Verma 

I know, but this needs to be provided, when will it be provided.

How is this in the process, this all needs to be defined by @Konrad

Otherwise the solution is general, I know we provide guidance, but he needs to identify a seperator.

0 votes
Answer accepted
Shikha Verma
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.
August 20, 2024

Hi @Konrad You can try this:

  1. Trigger: Issue transitioned (B1 to Accepted)
  2. Branch: Branch on linked issues (Linked via A1)
    • Condition: Linked issue is in project B and is not B1
  3. Action: Transition issue (B2) to "Rejected"
Marc - Devoteam
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.
August 20, 2024

Hi @Shikha Verma 

Both issues B are in project B, then based on your suggestion, they would need to have an unique identifier, otherwise this rule will only work once.

 

Like Rilwan Ahmed likes this
Konrad
Contributor
August 20, 2024 edited

Hi @Shikha Verma ,

Can you elaborate on step 2 please. I tried the 'Linked Issues' (from 'type of related issues' field) however that only works on direct links, that is when B1 transitions the A1 will transition but not the B2.

 

Edit:

I tried Condition, JQL condition: 

project = B AND issue in linkedIssuesOf("{{issue.key}}") AND status != "Rejected"

for instance

Shikha Verma
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.
August 20, 2024

Hi @Konrad You can achieve this by JQL. Please try project = B AND issue in linkedIssuesOf("issueKey = {{triggerIssue.issueKey}}", "relates to")
Hope this will help you!

Like Konrad likes this
Marc - Devoteam
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.
August 20, 2024

HI @Konrad 

Also think about, what will happen if users add more links to issues A1.

They will be impacted as well if the same link type will be used.

Like Konrad likes this
0 votes
Shikha Verma
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.
August 21, 2024

Thank You, @Konrad, for accepting the answers. It will help others!

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.
August 21, 2024

Hi @Shikha Verma 

When posting to community questions, please stay within the same thread rather than creating new ones for each response. 

That will help others reading this question in the future know if there are multiple possible solution approaches to choose from.

Kind regards,
Bill

Like 2 people like this
0 votes
Marc - Devoteam
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.
August 20, 2024

Hi @Konrad 

No there is no link between B1 and B2 if its not set.

The issues are both only linked to A1.

Automation could handle this, but you would need to have a link to B1 and B2

Konrad
Contributor
August 20, 2024

Hi Marc,

Thank you for the tip, however, the only link I would like to have is the one through A1.

 

Cheers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, ace, atlassian community event, donation, girls who code, women in tech, malala fund, plan international, kudos, community badge, badge, atlassian badge, International Women’s month, International Women’s Day, women's month, women's day

10 for Change at Atlassian Community Events

Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!

Join an Atlassian Community Event!
AUG Leaders

Upcoming Jira Events