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

Difference between Epic/Theme fields and New Epic functionality

shrikant vashishtha

I am using latest JIRA version. Though I like the new epic functionality, I get confused with Epic/Theme, Epic Link and epic name.

Simple idea is - if I map a user-story with an epic, that epic name and link by default should be visible in my user-story. Right now even after field customization I can only see epic link but not the epic name I mapped with.

The idea of Epic/Theme is manual and it's a label you place on user-story. Not sure why we are making it confusing for the people. Why can't we have one single Epic functionality

Accepted answers

Renjith Pillai

Epic/Theme is used by Classic boards. It is not used by the new boards.

The Epic Link is the one which is used by the new boards which get populated when you drag a story in the new board to the Epic on the side panel.

All comments

Renjith Pillai

Epic/Theme is used by Classic boards. It is not used by the new boards.

The Epic Link is the one which is used by the new boards which get populated when you drag a story in the new board to the Epic on the side panel.

shrikant vashishtha

Also how do I import NEW epic field with CSV import? Do I need to do it manually after user-stories are imported? Last but not the least, what's the use of Epic/Theme anymore in light of NEW epic functionality. Why create such a confusion. If that functionality is really desired what about giving it a different name?

shrikant vashishtha

In the classic view, how do I see the association of the NEW epic with the user-story.

All I see is the story number (NUT-117 for instance) in the Epic Link field which doesn't provide me the understanding of which epic it is unless I access that story number in a new browser tab.

Epic Link is not a HTML link also which I could click to see the relevant epic.

Renjith Pillai

You cannot do via CSV. You need to use REST - https://answers.atlassian.com/questions/115733/how-to-attribute-issue-to-epic-via-api

Renjith Pillai

When you click on the Epic/Theme field it opens a dialog which shows all the stories contained (or rather linked to it). You can also add the field to issue navigator.

Greg

How do I link an Epic to an Epic to create Epic Hierarchies like in old greenhopper?

Marina Garrison

I would like to know how to do this too but i don't think it's possible.

Greg

found an answer... Structure plugin... great tool and way better than the old native epic editor. This is the way to go.

Marina Garrison

Thanks for the info, unfortunately not avaialble for On Demand.

Contact Kintosoft

Maybe some from you migth want to take a look at the Links Hierarchy add-on for JIRA as it transforms Epic Links into regular JIRA links on the fly, so users are able to trace/visualize the hierarchy of stories, tasks, etc from JIRA and Agile just like were true links between Epics and its "children".

Kirk_3hqfcq

Here is a baseline explanation of the various Epic related fields and constructs:

1. Epic is one level higher than Task, Story, or Bug...out of the Box.

2. In a Classic Project, you connect your Task or Story to an Epic using the Epic Link field in the Task or Story. In a Team Managed\Next Gen Project, you connect your Task or Story to an Epic with the "Add Parent" link in the Task or Story.

3. When you link an issue to an Epic, it is somewhat confusing because an Epic has essentially two names. It has the Summary field which you might assume to be the name of the Epic, but to outside Issues, the name of the Epic is actually the "Epic Name" field. This is why most of us simply make the Summary field of an Epic match the Epic Name field of the Epic. That way we don't accidentally pick the wrong thing as a parent.

4. The Epic/Theme field is kind of a generic field. It does not create an inherent hierarchy. Some organizations even create another issue type above the Epic called a Deliverable, then they use the Epic/Theme field to indicate a conceptual Parent to the Deliverable...(which is extremely confusing but functional)

5. The other recommendations talk about how to gain access to the Epic/Theme field, but this answer describes the why and the hierarchy. (The hardest thing about hierarchy is pronouncing it.)