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

Inherit fields from epic to user story when the epic link is updated using the new automation engine

Bianca Sarmiento

How can I inherit fields from epic to user story when the epic link of the user story is updated? I am trying to do this in the new automation engine in JIRA by using the 'Field Value Change' trigger. However, when I select this trigger, 'Epic Link' is not an option to choose from in the 'Fields to monitor for change' drop-down. Please advise.

Accepted answers

John McKiernan

Hi @Bianca Sarmiento ,

This is a limitation at the moment I'm afraid. We are tracking it here: https://codebarrel.atlassian.net/browse/AUT-1264

This workaround should do the trick until it is fixed:

epic link.png

All comments

John Funk

Hi Bianca - Is this a Next-gen project? If so, Automation For Jira does not currently work with the Epic Link field.

Bianca Sarmiento

Hi John - This is for classic projects. See screenshot below for an automation rule I am trying to create for a single classic project.

Epic Link Missing on Field Value Change Trigger.jpg

John Funk

Yes, it is missing for me also.

I don't see anything in the documentation about it not being allows - unless I missed it somehow.

@John McKiernan - can you verify?

John McKiernan

Hi @Bianca Sarmiento ,

This is a limitation at the moment I'm afraid. We are tracking it here: https://codebarrel.atlassian.net/browse/AUT-1264

This workaround should do the trick until it is fixed:

epic link.png

John Funk

Thanks @John McKiernan !!

Bianca Sarmiento

Thanks @John McKiernan for the update.

With this workaround, will any update regardless if it is for a change in Epic link, count as a rule execution?

John McKiernan

Hey Bianca,

This is a good point.

It will count as an execution regardless. This wouldn't be the case with the 'field value changed' trigger as it would only kick off when the epic link is updated.

If your rule is only running across one project, it doesn't matter as you have unlimited single-project rules. However, if you are running it across many projects, it would start counting against your monthly multi/global rule executions.

Hopefully, we can get that epic link issue fixed soon so it is not a consideration.

Cheers,

John

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software