When you want to map two single-select lists or a two multi-select lists, your options for doing a ''value map'' would be to either do:
An **''Implicit'' value map**, where ALL items in both endpoints (for example: QC and JIRA) are IDENTICAL - this is great for long lists.
An **''explicit'' value map,** where you choose various pairs of values between the endpoints (QC and JIRA) for your mapped fields.
When you do an EXPLICIT VALUE-Map of the possible values for a single or multi-select field, you MUST have a corresponding map for ALL possible values, not just the commonly used ones. If someone adds new values to the list, they must be accounted for by revising the LINK (value maps) to accommodate them.
When there is a mismatch, you get errors during Sync.
After mapping and getting the link it working, you might get errors caused by any NEW items in the list on either side (for example QC or JIRA) side that are not ''value-mapped'' -- these will cause errors during sync.
This is why we recommend to try to do IMPLICIT Value maps (if you can) and use due-diligence to keep both lists the same in both endpoints (JIRA and QC). Also, the Admins should lock down user's ability to add items to the lists.
For a solution to having a VERY long list or ''too dynamic'' of a list, see ''ID field ''handshake''.