Automtion for Jira - access Components of linked issues

[Jakob KN]

Hi Folks, 

I'm trying to set up a rule, which copies components when issues are linked.
Since components are project-specific, I'm not sure if it's possible to copy the values to the components field, alternatively copying to the labels field would work as well.

I have 2 projects: Project A and Project B.
The rule should trigger when an issue is linked between the two projects, but only in one direction. Components from project B should be added to linked issues of project A, but not the other way around.

I'm not seeing any options to accessing values of linked issues through the standard options, is there any way of doing this through the advanced options?

Any help or advice would be much appreciated!

[Parvaneh Zand]

Hi @Jakob KN ,

- You can't add component of Project A, to an Issue from Project B. As you said they are project specific.

- Automations are limited, there are plugins such as Automation for Jira, by which you can add actions on components (for link issue trigger)

[Jakob KN]

Hi Parvaneh, 

I suspected it might not be possible to add to the component field. 
Copying the value of Project B'd component field to Project A's Labels field would be an acceptable solution.

I don't  think it's possible to copy from project B's component fields from the option in your screenshot. 

Do you know if this is possible through the advanced options?

[Parvaneh Zand]

As much as I know, project automation works for peer to peer field types, I mean if you add a branch rule for linked issues, it will update component/label , just like trigger issue's component/label.

I think the solution can be achieved with Scriptrunner plugin,

There are many related questions in community:

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Updating-Custom-Field-based-on-Linked-Issue/qaq-p/656809