...
When you restore from a Jira backup, custom fields in the source Jira instance are re-created in the target Jira instance, but with different IDs. Also restored is a database table that contains Risk Register's internal configuration, which references particular custom field IDs. You therefore end up with Risk Register's internal configuration 'pointing to' custom fields by IDs that don't exist in the target Jira instance.
Step-by-step guide
Here's what you need to do to fix the problem. Unfortunately, it involves manual changes to the contents of a database table; and in the future we may offer a way to do this through the Jira user interface, but for now we have to break out some SQL.
...
Once you've updated the contents of the AO_A29AEA_CONFIG table, you should re-run the Jira indexer.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...