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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Epic Name suddenly a REQUIRED field

Can't enter any Stories into the system, can't edit anything!!!!!

I've luckily been able to resolve this by hitting the Restore defaults option in the Admin - Issues- Field Configuration window.

But have no idea how this happenned,

Epic Name is a LOCKED field, this morning suddenly everyone started dropping me mail, calling, IM "I can't enter a new story, Epic Name required".

I found Epic Name in Field Config, and yes it said REQUIRED LOCKED, but I couldn't change it!

I only use the default Field Configuration, and as I see it there is no way to set it to REQUIRED. I can set other fields to required but this field is locked. I called Atlassian but only got a machine, I couldn't talk to anyone, so logged an Issue, but have not heard back....I really don't want this to happen again.

7 answers

1 accepted

5 votes
Answer accepted

Atlassian looked into this for me, looked at the logs etc and no dice, they can't figure out how it happened. I was changing the fields available on the screens and somehow it triggered this. I eventually had to go into Administration > Issues > Field Configuration > Configure (Default Configuration) and reset the default settings - luckily I hadn't changed anything.

Atlassian informed me that this was a side effect of an update that they did on the On Demand version (the one that I'm using). They were able to correct it for me.

Wild. Just happned to my downloaded version - thankfully for only one project. I suspect it may be because the story issue type in the project contains this field from an external system import. Going to try clearing that out to resolve. Otherwise this is pretty hosed.

Pretty bonkers but I just did this ( and then was able to return the field to being optional for stories (or whatever issue type should NOT require epic name to be defined). Filing a bug for this.

Had the same problem with on a fresh online instance. Reset to default settings helped.

Deleted user Feb 17, 2016

Don't know why you should have to post an answer.  Atlassian should have people constantly monitoring these groups and posting answers for all their users.

But thanks for your effort!  It really helps.

Thanks to your comment I reset to default settings and it worked. thank you.

Had same problem while moving Epics from one project to another: "Epic Name is required" even with Retain option checked.
Solution from @Rog1 worked, Tks !
into Administration > Issues > Field Configuration > Configure (Default Configuration) and reset the default settings


Screenshot 2019-05-29 at 10.10.02.png

I had a similar problem - don't know how it happened, but was able to remove the story issue type by unlocking the field, making the required changes to it, then locking it again:

Deleted user Feb 17, 2016

That article won't help cloud users, who can't modify the tables directly.

0 votes
Timothy Community Leader Jul 18, 2013

Check whether the Epic Name field has been made available to the Story issue type.

Hi Timothy,

When I look in Admin - Issues - Custom Fields

I see Epic Name with the Epic and Story Icons, but I can't edit, it's locked (and now fortunately not required) Any idea how anyone made it required?? If this happens again during our rollout we're going to lose some fans!



I would also like to know why Epic Name became Required, even when creating stories, all of a sudden. I have tried removing it from all screens and from the issue type field configuration, yet it annoyingly remains.

Why should I have to specify an Epic Name when creating a Story? There is no agile practice that mandates Epics for all Stories. Epics are only needed when necessary.

More annoyingly, why should Epic Name be required when I have already specified an Epic Link? Has JIRA gone coocoo?

Just wanted to add that this also happened suddenly on my default configuration scheme by marking it required. I had to go and remove the required field.

I have a hint, that helped in my situation.

Epic Name was suddenly required. After disabling in in the Tempo Plugin as exported field, it was no longer required

I restored defaults and it works fine, but you could be possible right

Hey!! Thanks for the tip, My Epic Name had become REQUIRED which meant i could not make any new Epics 'because you cannot link an Epic to an Epic!  your hint worked. I am far too timid with JIRA to press the "default settings button" but it worked.  Thanks for the message. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,664 views 22 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you