Automation sets Issue A as blocked when Issue B is linked to it as a blocker

[Dana Pliavinska]

Hello there, I need to create an automation rule that sets Issue A as blocked when Issue B is linked to it as a blocker = blocks Issue A. But as I see, this rule does not work correctly or I can even say vice versa. Can you help please me how to deal with this?

[Bryan Trummer - ReleaseTEAM · Accepted solution]

Hi @Dana Pliavinska - If I am understanding what you are wanting to do here you need to reference the destination issue per this message in automation.

Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

So I believe you want your automation to look like this just with the transition being to Blocked.

[Dana Pliavinska]

Thank you @Bryan Trummer - ReleaseTEAM !!Looks like now it's working! :)

[Walter Buggenhout]

Hi @Dana Pliavinska and welcome to the Community!

I don't quite understand what you are trying to do, to be honest. That is most likely my bad, but can you describe your desired scenario step by step?

What I now see from your automation rule, is the following:

1. someone links an issue (A) to another issue (B), with a blocks issue link.
2. This automation rule kicks in from the issue that was linked (A) to the other one (B) and updates the status of that same issue (A) to blocked

How does that differ from the actual behaviour you would like to see?

[Dana Pliavinska]

Hey @Walter Buggenhout 
I'll try to explain my problem this way:
We have Issue A (TP-22 at the screen) that is blocked by linked issue B (TP-24). I need Issue A to be moved to Blocked status when it's being blocked by some linked issue. But now we see that the rule moved blocking issue = issue B (TP-24) to Blocked status. Is it more clear now?