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

[Sierra]

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 ?

[Mark Segall · Accepted solution]

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

[Saurabh.Sharma · Accepted solution]

[Saurabh.Sharma · Accepted solution]

HI Sierra,

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

Thanks,

Saurabh

[Kat Jansen]

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:

Any advise?

[H Guy]

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!