Automation to populate field with linked issue data contingent on linked issue type

Question

Hi all,

I'm wondering if it's possible to set up an automation which takes key info from linked issues (ID, name, status) and populates this into a field on the issue but contingent on the linked issue type.

For example I have central issue A, with a custom field "Important Related Tasks". This field will be periodically updated and published in a summary table on Confluence.

Issue A has 3 different types of linked issues only one type I care about for the purpose "Important link type".

I want to populate "Important Related Tasks" with the meta-data above but only from "Important Link Type".

How would I do this?

Bill Sheboy · Answer

Hi @Fernando Eugênio da Silva

I believe for this scenario, the intent is to update the field in "issue A" and not the linked issues.  Rather than using a branch on linked issues, the rule could gather them with the Lookup Issues action and use JQL with the linkedIssues() function to find the correct one(s).

Kind regards,
Bill

Fernando Eugênio da Silva · Answer

Hey @Alex Anderson . Welcome to the Atlassian Community!

If I understood correctly you're trying to copy the field value "Important Related Tasks" from the Issue A to the issue linked through Important Link Type.

In this case, you should try to start creating a simple automation like this:

- Trigger > Field Value Changed > Select the field Important Related Tasks

- Condition > Related issues condition > Select Linked Issues > Select the Link type you want to validate which is Important Link Type > Are Present

- Add a branch > Select the Linked Issues in the Branch > Select your Linked Issues Type which is Important Link Type

- Inside the branch select an Action to Edit Issue > Select your Important Related Tasks field > Click on 3 dots and change to Copy from Trigger Issue.

At the end of the day your conditions and branch it must be similar with this image:

Ps.: If your issues are from multiples/different projects, ensure that your rule scope is Global.

Hope this helps you