Synchronization breaks after changing the item type

Problem

During continuous synchronization, users might attempt to change the issue type or workitem. If the item was already synchronized, the TFS4JIRA overview (log) section displays a message similar to the following:

Failed to update Azure work item: TF4<itemid>: Invalid field status 'InvalidType' for field "System.ld'.

Solution

Changing the issue type or workitem time for an ongoing synchronization can be tricky. Below are two ways to implement this requirement to avoid synchronization issues.

1. Manual change - change on both sides:

   1. Ensure that all item types are mapped correctly in TFS4JIRA.

   2. Once the item type is changed in one instance (ADO or Jira), it should also be manually changed in the other (ADO or Jira) for the synchronization between those items to continue.

   3. Other configurations such as workflows, fields, and filters (if any) might need to be reviewed and updated to continue synchronizing the items.

2. Change the issue type using automation for Jira:

   1. Ensure that all item types are correctly mapped in TFS4JIRA.

   2. Instead of manually changing the item types in both instances, automation can help close that item with a comment and create a new one with the necessary fields copied.

      1. Here is an automation example that can be imported:

   3. Other configurations, such as workflows, fields, and filters (if any), might need to be reviewed and updated to continue synchronizing the items.

Open

The following screen recording provides an example of this process:

Open

 Related articles