Mapping Error: Jira Align Connector Skips Unrecognized Jira Field Types

Jira Align's Jira Software connector is documented to skip records when it encounters an unrecognized Jira issue type or custom field type, logging a mapping error rather than failing the entire sync batch. Because unsupported fields are silently ignored rather than raising a hard error, excluded data may not be immediately apparent.

The unresolved behavior concerns concurrent modifications. When a story's story points are updated in Jira Software and its scope is adjusted in Jira Align within the same sync window, the platform relies on a last-write-wins strategy. The product does not expose a deterministic conflict-resolution policy; instead, which value becomes authoritative depends on sync timing and connector configuration.

Version-sensitive behavior adds further uncertainty. Different Jira project types expose different field models, so the connector may behave differently depending on the target project configuration. Administrators can configure field mappings to reduce conflicts, but mapping alone does not resolve the underlying ambiguity when both systems modify the same record simultaneously. Specific connector versions and sync intervals may alter observed behavior.

Given these constraints, how should teams determine which system's estimation value persists after a concurrent update? Does the connector's skip behavior for unrecognized fields interact with conflict resolution in a way that amplifies data loss? What verification approach can confirm whether a specific Jira Align release applies last-write-wins deterministically or leaves the outcome dependent on connector scheduling?