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

Change the name of the "Epic Name" field

Richard Kersey

How can I edit the name of the "Epic Name" field. I changed the name of the issue type "Epic" to "Whatever I Want It To Be", but still Jira uses "Epic" in the issue fields. (Also "Epic Status", "Epic Color", "Epic Link").

You would think that if you change the "Epic" issue type name to something that it would update that word "Epic" everywhere... but nooooooooooo. Like everything else in Jira it has to be hard to impossible to configure.

I can almost guarantee before even asking this question, that the system field "Epic Name" cannot be renamed to anything else, because it says, "Locked" next to it, but I'll go ahead and waste my time anyway to see if Atlassian could possibly take their heads out of... you know what I mean.

(Everyday, the choice to use Jira seems like more of a mistake, and that we should just bite the bullet and get out of here)

Accepted answers

Jack Brickey

Hi Richard,

you are correct. While you can change the Epic title to something else it will not extend to Epic fields: Epic name, Epic link, Epic status. TBH, I think Atlassian should not allow changing the Epic title at all. It causes confusion and potential issues.

All comments

Grigory Salnikov_0hffsd

Hi @Richard Kersey and welcome to the community!

Just wondering, in what scenario would you like to change that name?

P.S. And yes, you are right. This filed is locked meaning you cannot change it. But it is done for a good reason.

Jack Brickey

Hi Richard,

Richard Kersey

I would like to change the word "Epic" in all scenarios everywhere to something that is better suited for our teams usage of the Jira tool. If I want to call "Epics", "Projects", or "Containers", or "Anythings"... then I should be able to. Jira should not force nomenclature. period.

Why do you feel there is a good reason to control every one's conventions? As if you know better for everyone in all scenarios what they "should" be doing.

Grigory Salnikov_0hffsd

Jira is a flexible tool to build any type of structures with any names you like upon it but some things should not be changed, I guess.

Do you feel the same irritation towards traffic lights colours? Or maybe a programming language's syntax? Here it is not the same but close to it.

Grigory Salnikov_0hffsd

By the way, if you do feel that it is a really good idea you can always create a feature request and people who feel the same will vote for it.

Richard Kersey

Right... Atlassian wants to make it customizable but doesn't seem to understand that once you do that it means you've opened it up to needing to make much more customizable than what you might originally open up to customization.

Overall, if I could go back 3 months, I would have chosen Monday.com or Asana. Would have at least gave them a good testing before I got knee deep in this garbage product.

Jack Brickey

There are a lot of good apps out there and they all have positives and negatives. I like Monday but IMO it isn’t a replacement for JSW or JSM, at least for my use cases. Never played w/ Asana. 3 months isn’t a long time so if you find another app works better then it isn’t too late IMO. However I think it is important to understand that there will be things you don’t like about the other options too. IMO Atlassian creates very compelling solutions at a competitive price point. More importantly, the invest a ton into continuing to advance these solutions, which is very important to me.

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