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

Do we need any special permissions to unlock a locked field? E.g. Epic Name

Fox Chen

We need Epic fields to apply to a new Epic issue type, however, Epic fields are locked, we cannot add the issue type into the context at application level.

I see the document https://confluence.atlassian.com/jirakb/how-to-unlock-a-locked-field-779158866.html.

We would like to know if any special permission to possibly unlock a locked field at application level or to run those queries?

Additionally, in the documentation, it mentioned:

These fields will be locked again on startup by automated tasks within plugins.

What does it mean?

Thank you.

Accepted answers

Alexey Matveev

Hello,

There are no special permissions to unlock a field. The only way to do it through the database. Database access is only allowed on Server, which means that you can not unlock a field on Cloud.

And if a field is locked, it means that the developer of the app, who added the field, decided, that this field should never be changed by a user, and if the developer did that, there were reasons. That is why do not unlock locked fields.

All comments

Alexey Matveev

Hello,

There are no special permissions to unlock a field. The only way to do it through the database. Database access is only allowed on Server, which means that you can not unlock a field on Cloud.

Fox Chen

Hello Alexey,

Thanks for the answer. But do you know "These fields will be locked again on startup by automated tasks within plugins." What does it mean? If it means as soon as Jira restart, the fields will be locked again? This is done without any other plugin needed, right?

Should be no harm to apply the locked field to a new issue type, right?

Alexey Matveev

If plugins have such automated tasks then the fields will be locked after start. For Jira Software it will not be locked. At least I already unlocked this field and on startup this field stayed unlocked.

The Epic Name field by default is available only for Epics. You should not add it to other issue type, it can influence the work of Jira Software. Better create a new field and use it for other issue types.

Fox Chen

We have 2 issue types for Epic, but Epic fields only applied for one of them which I don't know why it setup in this way by former admin.

Creating a new field is possible to make the new Epic type working like the other one? My problem is actually the issue with new Epic issue type will not show in Epic Panel and the Epic link. So Epic fields are NOT mandatory to make Epic issue working as expected?