Epics - Team Managed Project

[Jenn]

I am using a Team Managed Project. I can't seem to get the Epic Link or Parent Link added to the card. Is that possible?

[Trudy Claspill · Accepted solution]

Hello @Jenn 

What problem are you trying to solve by adding those fields?

The parent Epic information should be displayed by default without you having to add anything.

[Jenn]

Hi Trudy,

The developers are trying to work in sequence based on epic/parent link. Its unfortunately not part of the default. This is a team-managed, kanban board. 

[Trudy Claspill]

Hello @Jenn 

Can you tell us what type of project you are using; Service, Software, or Business/Work Management? If it is one of the first two, that will be shown in the navigation pane on the left at the top below the Project name. If it is a Business project then the navigation options are displayed horizontally at the top of the page rather than in the navigation pane on the left.

In a Software Team Managed project, the Summary of the parent Epic of an issue will automatically display in a card thus:

In a Business/Work Management Team Managed project, the parent Epic information is not displayed in the child issue card, and the field for the parent Epic ID or Summary is not available to add to the card layout. If this is your project type, you could work around this by adding a custom short text field, using automation to copy the parent Epic ID or Summary to the custom field in the child issues, and then add the custom field to the card display.

[Alex Koxaras _Relational_ · Accepted solution]

Hi @Jenn 

On team managed projects these fields do not exists. It's only the parent field. The two fields you mention still exists on company managed projects, but this shall pass as well (https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/).

[Charles Southworth]

The fields do not exists and cannot be added. Use parent.

The 'work around' to manually add them as text fields, has data integrity implications when things get renamed as the changes will not flow.

If using 'Parent' then the using additional JQL for 'type = epic' may allow consistent reporting across team/company project types.

When constructing a dashboard use a reference JQL to your main filter "Filter = ##### and Type = Epic" then you only need change the base filter when updating dashboards.

Good luck to everyone that has landed on this thread!