Epic name put on required after reboot

Question

When our Jira instance gets a reboot, the field "Epic Name"  is automatically put back on required. Even when we unlock the field, put it on optional and lock the field again.

Why is this put back on required every time and how can we prevent this from happening again?

Nic Brough -Adaptavist- · Answer

Epics need the epic name field to be filled.

Stop using epics in business projects, you clearly don't need the functions they provide.

Lander Albrecht · Answer

It doesn't get locket automatically when it's unlocked in db. The Epic Name just gets put on Required everytime.
We have a business project and where this field has no added value so we removed it from the screen, but as it has a null value, people cannot create those tickets.

Nic Brough -Adaptavist- · Answer

The field is locked as part of the startup because it should be locked to prevent admins making changes that break things.

The field is mandatory for a good reason - it's required by the Epic functionality.  Why are you unlocking it?