nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Automation - Epic not being set when child issue is created

Robert Nordstrom

Hello, I hope someone can help us. We've been using JIRA Automation for several years. Recently, we noticed that the child issues being created were not getting linked to the Parent Epic. In investigating, we found the message about:

Epic Link will soon be replaced with Parent. Update to Parent field to prepare for these changes.

In our original child issue Epic Link, we had it set to "Copy from trigger issue"

2025-02-21_JIRA Automations.jpg

We tried setting the Epic Link to "Copy from parent" as the message indicated and reran the automation with the same results. The child issue is created but is orphaned with no epic link.

Accepted answers

John Funk

Hi Robert,

The message was not that you should use Copy from parent for the Epic Link field, it's that you need to replace the Epic Link field with the Parent field. Then you can use the Trigger Issue as the parent value.

All comments

John Funk

Hi Robert,

Robert Nordstrom

Thank you, John! That makes sense. I still don't understand where to change the Epic Link field with the Parent field.

John Funk

Click on add fields, then click off the Epic Link field and select the Parent field in the list.

Robert Nordstrom

Got it! Thank you , John!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud

jira-automation