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 set the Epic of an issue created with automation in a Next-gen project?

Presten Swenson_gbhxr3

I am using automation to create an new issue in the Kanban board of a Next-gen project. I would like to set the Epic of this new issue to the same Epic as that of the trigger issue or the parent of the trigger issue (when the trigger issue is a sub-task). How can this be done? Setting the Epic Link field of the new created issue does not seem to work.

The only workaround I have found is to clone the trigger issue and then edit the fields of the newly created issue. In that case, the Epic is set automatically. There must be a simpler way however and this does not work when the trigger issue is a sub-task.

Thanks in advance for any suggestion.

Accepted answers

Trudy P Claspill

In a Team Managed (previously known as Next Gen) project, the child issue notes its parent Epic in the Parent field rather than the Epic Link field.

I don't think it is possible to set that field via Automation for an Epic/Child Issue relationship in a Team Managed project, but I have not actually tried it. I know it is not possible to directly edit that field through the UI to add an issue to an Epic in such a project.

All comments

Trudy P Claspill

In a Team Managed (previously known as Next Gen) project, the child issue notes its parent Epic in the Parent field rather than the Epic Link field.

Presten Swenson_gbhxr3

Thank you Trudy. It is interesting to me that Epics are treated differently for Team Managed projects. The Epic filter fields don't work and the automation does not have the ability to identify the Epic as the top of the hierarchy that Jira explicitly states exists. This seems like a bug to me.

Trudy P Claspill

The "architecture" and support thereof for Team Managed projects is relatively (a handful of years) new in Jira. They have not refactored all existing features to work with that new architecture. There are many things that can be done with Company Managed projects that can't be done with Team Managed projects.

Regardless, I would encourage you to use the "Raise a Bug" option under the "?" button (in the upper right corner of Jira, next to your avatar) to raise that issue to Atlassian directly. They may already have an open bug/change request for it.

Bill Sheboy

Hi @Presten Swenson

Yes, and...to what Trudy notes: there are already a few open suggestions and bugs on this symptom, including this one: https://codebarrel.atlassian.net/browse/AUT-2090

Kind regards,
Bill

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

jira-software-cloud