To use project fields as custom fields, we need to do an update process after a project field modification because we need to deploy project changes to issues.
Visually nothing has changed on the Edit project fields page, but when you click on the Save button and if you changed a project field that is used as a custom field, the update process will be launched. A user can see the status of this update on the Project fields page.
These are the different messages that the user could see depending on the status of the update process: Please, keep in mind that these messages will only be available in the database.
Updating in progress
The update process is active in the background. The process will take approximately as long as a normal JIRA re-indexation of a project. The duration of the process will also depend on the server architecture, the project issues, and the number of custom fields.
Waiting for update
The update process is in a queue.
The update process has failed. You should contact your JIRA Administrator.
It's important to realize that our priority is a positive user experience. For this reason, the update process is launched automatically in the background so that you may continue working normally. But, keep in mind that the information in the custom fields may not be correct until this process has finished.
To keep JIRA fluidity, there can only be three background update processes at the same time. If more updating process are needed, Profields will queue them. Then, when an active process ends, the next process in the queue will be activated.