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.
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.
Pretty bonkers but I just did this (https://confluence.atlassian.com/display/GHKB/How+to+unlock+a+Locked+field) 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.
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.
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:
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? https://confluence.atlassian.com/display/GHKB/Epic+Name+vs+Epic+Link
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.
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs