Issue Summary

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Create a field mapping for Priority (or custom dropdown field) in Field management tab.
2. Map field values in the modal and set a 1:many relationship (e.g. map JA Low to JSW Low as default and Lowest).
3. Create a Jira epic and assign it a priority of Lowest.
4. Update the corresponding feature in JA (e.g. change the description).
5. The connector sync overwrites the Lowest priority value and assigns the default value of Low.

Expected Results

The Jira epic priority would remain as Lowest, the connector should not overwrite existing values with the default. The connect should only assign the default value if the record does not have a value.

Actual Results

The below exception is thrown in the xxxxxxx.log file:

...

Workaround

Do not implement 1:many mappings in the field value mapping modal.