Automation rule for sub-task, copy parent component field value

Sierra
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 6, 2022

Trying to figure out how to create an automation rule that sets my sub-tasks component field, the same as whatever parent issue type I'm using has. 

This one of the many rules I've tried , am I close ?

Rule.png

Rule.png

3 answers

3 accepted

3 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 6, 2022

Hi @Sierra - You'll need to change the Edit Issue action to copy from Parent

2 votes
Answer accepted
Saurabh.Sharma
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 6, 2022

copy component from story to subtask.jpg

2 votes
Answer accepted
Saurabh.Sharma
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 6, 2022

HI Sierra,

Please try like {{issue.parent.component/s}} . It works for me.

Thanks,

Saurabh

Kat Jansen May 23, 2024

We've got an automation rule like this but it's breaking when the parent has multiple components.

I tried this trick and I get the same error.

Couldn't edit the Components field - the component doesn't exist
No fields or field values to edit for issues (could be due to some field values not existing in a given project):
Here's the Automation Rule:
Copy Components to Sub-Task.png
Any advise?
Like H Guy likes this
H Guy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 6, 2024

I have the same problem. if the parent has multiple components I cant get the rule to work with either of these smart values:

{{triggerIssue.components}}

{{triggerIssue.components.name}}

{{triggerIssue.components.name.join(", ")}}

{{issue.parent.components.name}}

{{issue.parent.components.name.join(", ")}}

Someone please help!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events