In jira data center version copy from parent is not working

Question

hi community,
I'm currently using jira data center version, workflow hierarchy is like initiative->epic->story->sub-task. 
I'm working on automation where I need to pull the labels field data when the issue is created as a child. 
When a use "Copy from Epic" it's working fine but only to epic to story level. but When I use "Copy from Parent" this is not working properly at all, audit logs says success but it's not working as expected.

Bill Sheboy · Answer

Thanks for the rule image and additional information.  And, I am using Jira Cloud, not Data Center, so please test any changes I suggest.

The Issue Created trigger can fire so quickly it may not yet have all data for the issue.  I recommend adding the Re-fetch Issue action immediately after that trigger.  This will slow the rule a bit and reload the data before it proceeds.

Next, have you verified which field is used to connect the Initiative to child Epics?  It may not be "parent" but be "parent link" instead.  In that case, you may need to use the Lookup Issues action with JQL to get the Initiative, and then add that data for the labels.

mohit jangid · Answer

Hi @Bill Sheboy 
My automation is pretty simple goes like this:

Audit Log: It shows success but nothing is coming from parent side that' s why I use both "Copy from Epic" & "Copy from parent", When a use "Copy from Epic" it's working fine but only to epic to story level. but When I use "Copy from Parent" this is not working properly at all.
Means from initiative, data is not coming to epic level

Bill Sheboy · Answer

Hi @mohit jangid

For a question like this, context is important for the community to help.  Please post the following:

* 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.

Until we see those...

For Data Center, the relationships between the different issue types you note is handled by different fields, and so your rule will need to handle those.  For example, in some cases it may need to branch with JQL to reach the issues and then smart values to copy the values.

Are you trying to create a single rule to update all possible level pairs (e.g., initiative > epic, epic > story, and story > sub-task) or multiple rules?

Kind regards,
Bill