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?
Hi @Marc - Devoteam you can achieve this by using a Unique Identifier.
project = B AND "Unique Identifier" = "Value1"
to target B1 and a separate condition for B2 with "Unique Identifier" = "Value2"
.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Konrad You can try this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank You, @Konrad, for accepting the answers. It will help others!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.