It should work from the blocking issue as well, automatically identifying the issue that was blocked. I'm working in Jira Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anna "CoPandamonium" -- Welcome to the Atlassian Community!
That could be done using an automation rule with a Work Item Linked trigger, and remembering to check the correct link direction. If your work items could be multiple projects, the rule will need a multiple-project or global scope, and you Jira Site Admin will need to make that change.
I recommend trying to create the rule and if you run into challenges, post images of your complete rule and the audit log details so the community can offer suggestions.
To get you started, please see this documentation:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please note my earlier comment about link direction, as that impacts which work item is the "trigger" and which is the "destination" for this rule trigger:
Consider two work items: ABC-123 and ABC-456.
When viewing ABC-123 and one adds a "is blocked by" link to ABC-456:
If you start with ABC-456 and add the opposite link direction of "blocks" the result is the same. The link direction in the site settings impact which one is the trigger issue.
For your scenario, you likely want to add a branch to the destination issue:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.