ResolveUpdateConflicts
Update conflicts can occur when importing changes for an already existing target item, if the same field value was concurrently modified in JIRA and in Codebeamer.
By default, conflict resolution works as follows:
• For single value fields, such as status:
◦ The new JIRA value has precedence.
◦ Any local field changes are discarded.
• For multiple value fields, such as assignee:
◦ The typically incremental JIRA changes are applied to the target Codebeamer field, for example add user "Zoltan Luspai". Conflicting local changes are discarded.
◦ Any remaining local changes are exported to JIRA if bi-directional synchronization is configured.
For a @CustomField extension wants to be involved in or take control of conflict resolution, it needs to provide a @CustomField.ResolveUpdateConflictsmethod
.
.The method has access to the following context information using parameters of the appropriate type:
• JiraImportController, to receive the controller of the current JIRA import.
• ProjectConfiguration or ProjectDto, to receive the target project of the JIRA import.
• JiraTrackerSyncConfig, to receive the target tracker of the JIRA import.
• TrackerItemDto, to receive the target tracker item, whose import is finished.
• TrackerLayoutLabelDto, to receive the target field, whose value was imported.
• List<IdentifiableFieldValueDto>, to receive the local field updates to be applied remotely.
• JiraRestClient, to receive the REST API of the remote JIRA instance from which to import.
• ImporterSupport, to receive the current importer.
• TrackerItemFieldHandler, to receive the handler for the current tracker item field.
The Checklist for Jira extension does not include a @ResolveUpdateConflicts method. If there are concurrent modifications, local changes to the target Checklist Wiki field are overwritten.
extension does not include a @ResolveUpdateConflicts method. If there are concurrent modifications, local changes to the target Checklist Wiki field are overwritten.