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; } } }

How to copy a custom field value from the Epic when a new story (Child-Issue)

Matt Johnson_gxav91

I'm trying to write an Automation workflow that copies a custom field from the Epic to the new Child Issue (Story) if the Epic has a value in the custom field. Here's the details of the workflow

However, when I create a new issue (using the Add a Child Issue from the Epic and the Automation fires it doesn't take any action.

Instead, it states that the 2nd condition (Epic exists) did not pass, when clearly I have an Epic as the Child Issue is being created from it.

Am I missing something?

Any assistance is greatly appreciated.

Accepted answers

Matt Johnson_gxav91

After speaking with Atlassian Support I was able to determine that there is in fact an association between Epic and Story in both Company and Team Managed project types and wanted to share this in case someone runs in to the same issue I had:

Cause:

the automation is attempting to perform the steps in parallel, which resulted in not finding the parent of the issue being created.

Solution:

Add a Action step: "Re-Fetch issue data" before referencing the Epic or Parent.

What the 'Re-Fetch issue data" function does:

The re-fetch action is designed to refresh and retrieve the most recent version of the data, ensuring that the automation has the latest information to work with. This helps prevent errors and inconsistencies that may occur due to simultaneous actions.

Thanks for the replies everyone! Atlassian definitely has a great support community!

All comments

Walter Buggenhout

Hi @Matt Johnson,

At first sight I cannot see anything particularly wrong with your automation. I built a similar rule to check what might be missing and did more or less the same. The only thing I am sure I did differently, was add a check on the created issue type, so I am sure that I am validating a story:

Screenshot 2023-07-19 at 20.15.29.png

Also, check the scope of your automation rule to make sure the linked epic is in a project that is included in that scope.

Hope this helps!

Matt Johnson_gxav91

Thanks for the reply, so when you did this it worked?

I did verify that the Project Scope is specified already. I deleted the workflow and started from scratch again. This time it took no action claiming the Issue did not match the 2nd condition (and: Epic Exists) when the Epic I created it from sure does exist.

Walter Buggenhout

Is your project team managed or company managed @Matt Johnson? In my setup it does indeed work, in a company managed project.

Matt Johnson_gxav91

It's a Team-Managed project. However, I'm writing this Automation in the Project, not under Global Administration. As I'm an Admin for our Atlassian Account I could try doing this at the Global automation level, but it seems odd that would be a factor in why it doesn't work.

Matt Johnson_gxav91

Cause:

the automation is attempting to perform the steps in parallel, which resulted in not finding the parent of the issue being created.

Solution:

Add a Action step: "Re-Fetch issue data" before referencing the Epic or Parent.

What the 'Re-Fetch issue data" function does:

Thanks for the replies everyone! Atlassian definitely has a great support community!

Walter Buggenhout

Thx for sharing, @Matt Johnson!

Michael Ludvigson_fzg9f3

wow, I was looking for something like this today and there was your solution! Thanks for posting the update from Atlassian Support too. Looks like mine are still not populating the underlying stories, after the fact. Am I missing something in my rules?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud