Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Epic names?


New to JIRA. 

Can anyone explain why epics have both a Name and a Summary? I find myself always making them identical. 

Edit: Never mind, I found this:


1 answer

1 accepted

0 votes
Answer accepted
Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 09, 2018

Epic name is what you see in the "Epic Panel" on a scrum backlog and also Epic name is used as the "Epic link" in the linked story.  Whereas Summary is just the normal JIRA field. 

Thanks. I'm just still not sure why you would want those things to be different....

Like # people like this



I know the difference but I always give for both the same name. Can I remove from the screen the Epic Summary? When I clone an Epic I find really annoying to change the two fields. I forget to change the summary. 

Did you try to remove it? 


Thank you and beste regards. 


What is the point of having two fields? I've seen two cases so far:

  1. The names exactly match. In this case, having the separate field is redundant.
  2. The names don't match, because someone renamed the ticket and didn't know the "Epic Name" field existed. In this case, having the separate field adds confusion when you're trying to autocomplete an Epic Link on another ticket.

Is there a valid use case for having two different names for the same ticket, where it also doesn't cause confusion?

Like # people like this

The confusion is caused by the "epic name" being used in the epic list and other places, but when you open the epic, it's the summary that's in big bold text.

The summary is used as the title, which is counterintuitive, and the name is given reduced prominence with muted text and lower in the page so you have to go looking for a reference to the thing you thought you just navigated to.

I find it really confusing and very annoying that the prominence is swapped depending on the context. It would be far better if the field used for the title was the same as is used elsewhere.

It's a seriously flawed design decision that leads to a dysfunctional UI (IMHO of course).

I use the "summary" as a title and give it the same value as the epic name to avoid confusion. The description contains the details. I also make sure the names follow a suitable hierarchy that follows a logical naming order, they are never "as an X I want to ... so that ...", that goes as the first line of the description.

Like # people like this

Where can I set that the title of an Epic issue will be Epic Name instead of the Epic Summary ?

Like Camila Zaze Guedes likes this

So it seems that the reasoning behind this is so you can have a shorthand name in the epic panel and epic link, which has logic to it.  However, life is all about tradeoffs and after being the company Jira guru for 6 years and training new teams to use it, this benefit doesn't outweigh the confusion that it creates.  There should just be one field called "summary," which is also used for epic panels and epic fields.  In other words, get rid of the epic name field.  If that causes issues in the underlying Jira architecture, those issues should be addressed in favor of reducing user complexity and confusion.  

Like # people like this

Agreed, this just causes needless confusion.  I set both the same.

Like # people like this

The font size of the epic label is the same as an issue's summary on the board and backlog views. It's redundant and a pain to update if you find yourself updating the summary when looking at the epic, then needing to go to the backlog > expand epics panel > expand epic > edit name and copy-paste the name to update. A waste of time. I too just name them the same as the summary and longer names have never been a problem.

Like Nicolas Degardin likes this

It looks like a legacy thing that makes any sense nowadays and Jira doesn't know how to solve it.


Same as 'Mark as Done' button at Epics grid.

Like Kwame Afreh likes this

I found this idiosyncratic behavior terribly annoying myself. For the benefit of other admins, here is the workaround I devised for myself. This should be added to your announcement banner. It hides the summary field whenever the Epic Name field exists and sets the value of the summary field to whatever you type in the Epic Name field.

function configureEpicNameInput(form) {
    if (form.length === 0) { return; }

    var epicNameInput = form.find("input#customfield_10104");
    var summaryInput = form.find("input#summary");

    epicNameInput.on("input", function() {
        // Copy the value from epicNameInput to summaryInput

    if (epicNameInput.length > 0) {
        summaryInput.closest("div.field-group").css('display', 'none');

AJS.$(function() {
    JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function(e, context, reason) {
        var $context = AJS.$(context);
        if (reason == JIRA.CONTENT_ADDED_REASON.dialogReady) {

// for static issue creation form (https:///secure/CreateIssue.jspa)

Please note this does not yet address keeping the two fields in sync when the summary field is changed from the standard view issue page.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events