Automation action Copy from parent doesn't seem to work?

[Craig Wells]

I've created an automation that upon creation of a subtask, it should automatically copy the parent task's Component field to the subtask. 

However, this doesn't seem to be happening for some reason. Whenever I create a subtask on a parent ticket with a Component filled in, it doesn't copy over the components. 

The audit log says that the operation was successful, which clearly it didn't do what it was supposed to do.

I've tried the following:

• If I set it to a specific component instead of copy from parent, the rule correctly applies the specified component to the subtask on creation
• Adding a refresh prior to the edit issues action doesn't do anything
• Switching it to a JQL condition (as it's currently set to) didn't make a difference. (Originally it was set to Issue fields condition where type was Subtask)

I'm at a loss as to why this isn't working. It's clearly identifying the ticket as a subtask upon creation, and when using a specified component works correctly. I do not understand why the Copy from Parent issue doesn't work.

[Craig Wells · Accepted solution]

Ok I think I figured out what was going on. I was attempting to build two automations, one that copies components on create and another that copies components onto subtasks when the component on the parent task was edited. Both automations were turned on. I think the second automation was nuking the component on the parent task whenever I changed it somehow and therefore when I created new subtasks, the first automation was correctly copying what was there, which was nothing.

When I turned off the second automation, the first one worked. Now I need to figure out how to setup the second automation.

[Craig Wells]

And I figured out how to fix the second automation by using branching. Thank you for the help.

[John Funk]

Great - glad you got that part working.

[Bill Sheboy]

Hi @Craig Wells 

I just tried your rule scenario, in a company-managed project, and it worked for me.  I included a Re-fetch action after the trigger to confirm the data re-loaded prior to the condition and edit action.

I recommend re-creating the rule from scratch to see if that helps, as rules sometimes get "glitched" and broken from too many edits.

Kind regards,
Bill

[John Funk]

Hi Craig,

Just reaching a bit, but maybe click the box to Add to existing values in the rule?