...
Application | Jira |
|---|---|
Platform | Server/Datacenter |
Cause
The issue occurs if the property configuration item access level of the custom fields is set to ADMIN on target and LOCKED on source. This difference is displayed in the deployment wizard i.e. target custom fields' configuration item access level and will be modified to LOCKED.
| Note |
|---|
Always back up the data before performing any modifications to the database. Test any alter, insert, update, or delete SQL commands on a staging Jira server/datacenter first. |
Solution
Steps to unlock the custom field from the database.
...
...