After the latest update to On-demand that came out 3/17/13 at 9:07pm, the Epic Field is now locked in field configuration and is marked required. Our company does not utilize the Epic field so no new issue can be inserted until this is resolved.
The "Epic" issue type is create and managed by GreenHopper, including the custom fields used to enhance the base issue type. The latest version of GreenHopper now locks these fields down, so I'm afraid you won't be able to change the configuration anymore. This is desired as we want to avoid misconfiguration which results in certain features not being available or working properly.
The Epic Name field you refer to is used to give an Epic a short, often one word long description of what the "feature" is about. The name is prominently shown on all issues in Plan mode, on the detail view as well as in the JIRA view issue page in the Agile panel. You can change it by using the dropdown of an Epic and choose "Edit Name":
We are experiencing that the "Epic Name" field is stuck in our Custom Field scheme, it is required and can not be disabled, yet we do not use and no not want the "Epic Name" field in that context. If disabling the ability to disable this field is a deliberate choice to help admins not get into trouble with their configuration, then it appears to have backfired, as there are now apparently 32 users following this question to reconcile their broken configurations ...
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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