When you apply a standard that merges values (see Terminology & Standards), Risk Manager moves work items to their new value in the background. If something prevents this, the Configuration page shows one of the messages below. Each message has a code you can mention when you contact support.
RM-MERGE-001: Some values were not merged
What it means: Some work items couldn't be changed, so they still have the old value. Common reasons:
The message lists each value that wasn't merged and how many work items still have it.
What to do:
Click View work items next to the value to open those work items in Jira.
Change the value on each work item by hand.
Delete the old value on the Configuration page and click Save configuration.
Until you delete it, the old value stays disabled (see below).
If a value shows no work items found with it, click View work items to confirm before you delete it.
If you need help, click Contact support in the message.
RM-MERGE-002: Merging values stopped
What it means: The move stopped before it finished. Some work items may still have a merged value.
What to do: Contact support and mention the code RM-MERGE-002.
RM-MERGE-003: Work items couldn't be moved
What it means: Risk Manager can't bulk edit work items on your Jira site, so the merged values kept their work items. Moving work items uses Jira's bulk edit, which requires the Make bulk changes global permission.
What to do:
A Jira admin grants Risk Manager the Make bulk changes global permission in Jira's global permission settings.
Open Terminology & standards and apply the values again.
Disabled values
A value marked Disabled on the Configuration page has been merged into another value, but some work items still have it.
Once no work item uses the value, delete it on the Configuration page and save.