Copy fields from EPIC to child

[federica.niero]

Hi :)

Scope: when I create an issue in an epic, the values of some fields set in the EPIC should be copied in the issue just created.

I tried this automation https://community.atlassian.com/t5/Jira-Software-questions/Copy-field-value-from-Epic-to-child-issue-with-automation/qaq-p/1421943 but it is not working.

What am I doing wrong?

I think this relates to the fact that the automation is not giving me an option to copy form the EPIC instead of the only option "copy from current issue"

Thanks to anyone who might gives some advice,

f

[federica.niero]

Solved:
re-fetch action after the condition 

[Adrien Low _ServiceRocket_]

Hey @federica.niero ,

Just wondering if you have tried to click on the section under the field name?

I can see that Epic issue is a choice:-

Hope this helps.

Regards.

[federica.niero]

Hi, thank you:with your suggestion I was able to find the dropdown menu to select Epic Issue :)
but at the end the Rule is not pulling out the expected outcome, so value in the fields are not copied.
anything else I could try?

[Bill Sheboy]

Hi @federica.niero 

Is this rule running in a Company-managed or a Team-managed project?

Would you please post an image of the audit log showing the details for when the rules but does not copy as you expected?

Kind regards,
Bill

[Deleted user]

Hi @federica.niero

Can you please share a screenshot of the audit log? It would help to identify what is failing.

Perhaps you can check if the fields are added to the screens that associate with the Child issue type that you are referring to.

Thank you.

[federica.niero]

Hi Guys,

here the screenshot for the audit logs although I don´t think is useful since it show "issues edited successfully" but in the end they are not in the child ticket.

to clarify this rule is setup under a project environment
currently the rule is disabled since is not working (latest audit log for config change)
should I test this again but I don´t get why I should get a different outcome with no edits on the rules.

[Bill Sheboy]

Hi @federica.niero 

I have observed that sometimes rules get "glitched" in Jira Cloud after too many edits, particularly to triggers and the sub-settings in actions.

Please keep this rule disabled, and then try to re-create it from scratch to see if it works as expected.

By the way, I asked if this is a company-managed or team-managed project as there some open defects "copy from epic" for team-managed:

https://codebarrel.atlassian.net/browse/AUT-2182
https://codebarrel.atlassian.net/browse/AUT-2090

Thanks,
Bill

[federica.niero]

Hi @Bill Sheboy , thank you so much for your advise.
I will try.
Between company-managed or team-managed I don´t know. where I can find this information?

[Bill Sheboy]

Hi @federica.niero 

I see you solved this with a Re-fetch action...which is a common need when using the Issue Created trigger as the event could fire before all of the data is available for use by the rule.  I recommend moving your Re-fetch immediately after the trigger, before any conditions.

To find the project type, open the left panel and look at the bottom to see if the project is Company-managed or Team-managed.

Kind regards,
Bill