Why isn't this Automation adding components automatically to new sub-tasks?

Question

I am trying to have a new sub-task automatically inherit the parent's component.

Why is the below automation now working?

Bill Sheboy · Answer

Hi @Darryn

Looking at the original rule you posted, it uses the Issue Created trigger.  That trigger may fire so quickly that some data may not yet be available to the rule yet.  This particularly applies to smart values like {{issue.parent}}, {{issue.subtasks}}, etc.

The "fix" for that timing problem is to always add the Re-fetch Issue action immediately after the Issue Created trigger.  This will slow down the rule a bit and reload the data before the rule continues.  Please try adding that action and re-testing.

Kind regards,
Bill

Trudy P Claspill · Answer

Has the rule undergone multiple edits? Sometimes rules stop working for non-obvious reasons after repeated edits. You might try creating the rule a new from scratch.

Can you check if there is more than one field named Component or Components?

Use the information from this page to print all the fields from a sample parent issue and subtask and review the output to see if there is more than one field with that name.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

You could also try using advanced editing with JSON to copy the values to the child issue.

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

Darryn_enaaej · Answer

Great.

Yes, the parent has a component (we use components as our different boards in our team)

Project Type: company managed software

I added log action with {{issue.parent.components}} and it appeared as an ID number! So I changed the code to {{issue.parent.components.name}} and it now appears as the name of the parent's component.

I also change my Then: Edit Issue fields to use code {{ parent.fields.components[*].name }} but even this didn't work - the components on the new sub-task are still 'none'.