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 do I attach created story tickets to an Epic through automation? Next Gen

Dean Panos

I'm trying to run an automation that creates story tickets when a label is inserted into the Epic as a trigger.

I've got the tickets being created correctly but the stories created are not being linked to the Epic that triggers the automation rule. I've tried through "Epic Link", "Epic Name", and "Epic Theme" fields but none seem to work.

The following information is not being passed:
Epic Link (Not linking the stories to the epic)
Producer (Custom field to be copied from the trigger, in this case the epic)
Brand Manager (Custom field to be copied from the trigger, in this case the epic)

Attached is a screenshot of the setup I use for the story ticket creation:

Accepted answers

All comments

Jack Brickey

Hi Dean,

have a look at a rule excerpt I have for doing the same...

Dean Panos

@Jack Brickey If you reference my screenshot in the original post, I have that circled field already set. It doesn't seem to work in next-gen. Am I missing something from your screenshot?

Jack Brickey

Ah, yes. That is correct. Epic link doesn’t apply in NG. I have not done so but see if you can reference via “parent”.

Dean Panos

@Jack Brickey "Parent" is available in the dropdown list but the issue is that "Epic Link" itself does not actually link issues into the epic despite the misleading name. Is there some code I can drop in to perhaps get the parent's ID and set the story to that ID so it properly links?

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