Resolution was not mapped

Symptoms

An issue does not get synchronized and appears in the troubleshooting section with the category 'Resolution was not mapped' and the message, e.g. 'Resolution at position -1 was not mapped to a local resolution because either the resolution list have different lengths or no default resolution was set'.

Cause

You are using a correlation mapping for the resolution field but one resolution was not mapped properly. This means the resolution was not mapped on either the sender or receiver side. A position of "-1" indicates that the resolution was not added on the sender side. A position of "0" or greater indicates that a resolution was not mapped at the same position on the receiver side.

Resolution

Check if you have added all resolutions to the correlation mapping. The following steps should be done in order to resolve this problem:

• If necessary, change the resolution mapping settings in the synchronization configuration
• After fixing your configuration trigger a resync for the affected issues, e.g. using a JQL filter like "key in (ABC-1, ABC-2)"