What is the difference between Copy from Parent Issue and Copy from Current Issue?

[Christopher Kim]

I have an automation rule that copies field values from the parent, in this case Epic, to the child (Task). 

The problem I'm running into is that when I add the custom asset field "Audit Control" it only gives me one option to "Copy from Parent Issue." But all the other custom fields (none are assets fields) that are successfully copying over are configured as "Copy from Current Issue."

What does each of these mean and why is it predetermined by the field I choose to use in the workflow?

[Bill Sheboy]

Hi @Christopher Kim 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

Copy from Parent always tries to copy from the parent of the issue being updated.

Copy from Current Issue copies depending on the scope withing the rule...Looking at this example:

• trigger: some trigger with an issue, such as Issue Created.  At this point, {{triggerIssue}} and {{issue}} (the current issue) are the same thing.
• condition: some condition.  At this point, {{triggerIssue}} and {{issue}} (the current issue) are the same thing.
• branch: to other issues with JQL.  At this point, {{triggerIssue}} and {{issue}} (the current issue) are the same thing.
  • action: some action inside of the branch.  At this point, {{triggerIssue}} and {{issue}} (the current issue) are different.  The current issue refers to each one branched-to as the loop processes.
• action: some action after the branch.  At this point, {{triggerIssue}} and {{issue}} (the current issue) are the same thing.

Regarding the options available for copying a field value during add / edit issue, I suspect that is just differences in the rule editor design and not "smart enough" to dynamically update.  Often the design can be worked-around by entering the smart values directly for the edit.

Kind regards,
Bill

[Christopher Kim]

Hi @Bill Sheboy

Here are some screenshots to my current configuration. It seems like a simple enough task but I'm stumped.

 Automation rule logs indicate that there is no issue to copy the asset fields from.

Another example would be the asset (previously known as insight) custom field "Product Category"

In one automation rule its configured as "copy from Current Issue" but in the other 

[Bill Sheboy]

I am using Jira Cloud, not Server version, and have not tried that with Insight fields.  

Have you tried using the advanced edit with JSON to copy the data from the trigger issue, rather than using the drop-down list of fields?