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

Epic names?

Steven Battisti

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: https://community.atlassian.com/t5/Jira-Software-questions/Epic-Names-vs-Summary/qaq-p/24899/jump-to/first-unread-message

Thanks!

Accepted answers

Tarun Sapra

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.

All comments

Tarun Sapra

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.

Steven Battisti

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

Mari Car

Hi,

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.

Mari

Trejkaz_qkegwg

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

The names exactly match. In this case, having the separate field is redundant.
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?