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:

[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?

[Jack Brickey]

I’m unsure how to solve this in NG as I haven’t spent any time with it. If I get a chance I will look into it a bit addictive get back to you here. If you have not already search the community for potential solutions. For sure Epic Link isn’t the way to go as it doesn’t apply in NG.

[Jack Brickey]

Well interesting. I just did a quick rule an in fact epic link did work so they must have fixed it.

Now I suspect there is more to your request but I will need to consider that tomorrow as I’m going offline for the night.

[Dean Panos]

@Jack Brickey I was able to get the epic attached, but the issue I have now is that the customfields I have in this project aren't being copied from the trigger issue.

Here's an audit log screenshot. Keep in mind we are using NG.

[John Funk]

Hey @Dean Panos  - Check the context foe each custom field to make sure they are available for the issue type and project you are using. 

Also, check the create screen to make sure those fields are available on the screen. 

[Dean Panos]

@John Funk I'm not sure how to check whether or not they are available for the project. Keep in mind this is a NG project so options seem to be limited. Those customfields are created through the Project settings > Issue types menu.

[Dean Panos]

@John Funk I misunderstood what you said. All the customfields are available to each issue type. They are shared.

[Dean Panos]

@John Funk After checking what the customfield ID is for each issue type, it seems that the value in the audit log screenshot is not the same as the value that the fields actually have. What could be the reasoning for that? We don't have duplicate fields. Should I try re-creating the fields?

[John Funk]

I would try this: Go to Settings > Issues > Custom Fields

For the first custom field, click on the 3 dots on the right side and select Context and default values

Then in the URL, replace the custom field id with one from the error message - for example 10601. And then press enter. 

What field is showing up? And do you have the right issue type and/or project in the context that is used in the card? 

Can you share a screen shot of that context page? 

[Dean Panos]

@John Funk That page doesn't seem to exist in NG projects. I checked the api and that field number "10601" doesn't even exist in any tickets in our NG project. My assumption is since we had imported some tickets from a non-NG project into a NG project it's causing an issue, but I'm not sure why that would cause problems with brand new tickets created.