nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to copy components from several issues to one single issue?

Valentin CHAPLET

Hi all,

I'm trying to do an automation when a specific link is created between two predefined types of issue (A and , I copy the components from issue A and paste them into issue B.

To do this, I created a lookup using the JQL query: issue in linkedIssues({{triggerIssue.key}}, ‘is mitigated by’) then I created an edit issue by modifying the component field with the following smart value: {{lookupIssues.components.name.distinct.sort.join(‘,’)}}

I tried several combinations, but I never managed to copy/paste the components. Either I've got an error "Couldn't edit the Components field - the component doesn't exist" (the issues are in the same project and share the same predefined components), or I have no action happening.

Thank you for your help

Accepted answers

Piyush Annadate _ACE Pune_

Hello @Valentin CHAPLET ,
Welcome to the Community !

You already did the conditions; additional you may need to do as below:

- Advanced Branching as"{{destinationIssue.components}}" and variable name as 'comDetails'
- Edit issue and add below in additional fields:

{
"update": {
"components": [{
"add": {"name": "{{comDetails.name}}"}
}]
}
}

Screenshot 2025-05-15 at 1.26.24 PM.png
In above, we are adding components to the exists, not overwriting them !

Note: 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}}

All comments

Piyush Annadate _ACE Pune_

{
"update": {
"components": [{
"add": {"name": "{{comDetails.name}}"}
}]
}
}

Valentin CHAPLET

Hello @Piyush Annadate _ACE Pune_ ,

Thank you for your reply, the explanation is really clear.

Alexander Hohmann

May I somewhat relativise the assertion '{{issue}} will always refer to the source issue'?

Actually, you could create a branch for linked issues and have that branch run through all the work items connected through a certain link type like 'relates to' or 'is blocked by'. In that case, to my knowledge, {{issue}} will refer to the issue(s) the branch is working on, and the triggering issue would be the 'triggerissue'.

rajeswari saravanan

Hi @Piyush Annadate _ACE Pune_

I tried to copy multiple components from one issuetype to linked issue.

below is the issue,

I have a query regarding two issue types: Process and Basic Data Task (linked via Related Basic Data).

A Process issue has a Component value set.
A Basic Data Task can be linked to one or multiple Process issues.
I want to copy the Component value(s) from the linked Process issue(s) into the Basic Data Task.
If a Basic Data Task is linked to multiple Process issues, it should copy and store the values from all of them.
This needs to be applied to existing issues (historical data) as well, not just newly created ones.

When I tried using automation rule for copy components, its not working for multiple issues.(smart value works for only one when using first - {{lookupIssues.first.components.name}} —-> this is working)

but not for bulk one.

need some help in achieving this.

Piyush Annadate _ACE Pune_

You can copy the components as 'Copy' from trigger issue

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

component

jira-automation