Linked Issue Update Automation

[John Lord]

Hello,

I am stuck on an automation I want to set up thats a little complicated. I want to set an automation up that when fields on the linked issue are updated, it copies the updated fields to the linked issue (I think the correct term might be parent issue).

For example: Project A requests support from Project B for an issue to be on the next release. Project B reviews and updates the fix version field to show this will be included in the 4/2/2024 release. When Project B updates that field, the original issue from Project A has the fixed version field to match what Project B put in the field. 

[Rebekka Heilmann _viadee_ · Accepted solution]

Hi @John Lord 

How are the two issues linked? Is it per "issue link" or are they in a parent/child relation (like Epic and Task or Task and Sub-Task)?

You would simply listen for changes in the field in Project B and then update any linked issues or parents/children in Project A. The problem is, that Versions are specific to a Project. You need a Version with exactly the same name in each Project before the global Automation Rule works.

You need to be Jira Admin to create global Automation rules that span 2 or more projects. The rule would look something like this:

Trigger: You watch changes in the Fix version field. You can restrict that to added values, specific Issue operations etc.

Condition: Check whether the change happened in Project B

Branch: Use "Branch rule / related Issues"
This works for linked issues (restrict on the correct type of link you are using) and also for Parent/children issues.

Action: Edit Issue fields
Make sure to Copy from Trigger Issue and un-tick the checkbox "add to existing values"