List of conflicts

Owned by Jonas Hallensleben
Jan 13, 2023
3 min read

Conflicts that can be resolved manually

The conflicts that emerge can be divided into two categories

  1. Conflicts that can be resolved manually by you

  2. Conflicts that have to be resolved with help from our support team

“A version with this name already exist in this project”

This conflict emerges when you try to rename a version in the “Source” project to a version name that already exists in the “Target” project. Jira does not allow you to have two versions with the same name in a project. To resolve this conflicts you have two options:

  1. Rename the versions in the “Source” project to a name that doesn’t already exist in the “Target” project

  2. Disable the synchronisation and manually remove the version from the “Linked” project.

“Cannot delete version(s) in project(s), it is used in one or more custom fields”

This conflict emerges when you try to delete a version that is used as a value of a custom field on an issue. We added this conflict as a safeguard to prevent the Version & Component Sync app from deleting potential valuable data. In order to resolve this issue you can take the following step:

  1. Disable the synchronisation and manually remove the version from the “Target” project.

  2. Manually remove the version from the custom field of the effected issues.

“Cannot delete version(s) in project(s), it is used as value of the Affects Version(s) field of one or more issues”

This conflict emerges when you try to delete a version that is used as a value of the Affected Version(s) field on an issue. We added this conflict a a safeguard to prevent the Version & Component Sync app from deleting potential valuable data. In order to resolve these is issue you can take the following step:

  1. Disable the synchronisation and manually remove the version from the “Target” project.

  2. Manually remove the version from the Affects Version(s) field of the effected issues

”Cannot delete version(s) in project(s), it is used as value of the Fix Version(s) field of one or more issues”

This conflict emerges when you try to delete a version that is used as a value of the Fix Version(s) field on an issue. We added this conflict a a safeguard to prevent the Version & Component Sync app from deleting potential valuable data. In order to resolve these is issue you can take the following step:

  1. Disable the synchronisation and manually remove the version from the “Target” project.

  2. Manually remove the version from the Fix Version(s) field of the effected issues

“Cannot delete component(s) in project(s), it is used as value of the Component(s) field of one or more issues”

This conflict emerges when you try to delete a Component that is used as a value of the Component(s) field on an issue. We added this conflict a a safeguard to prevent the Version & Component Sync app from deleting potential valuable data. In order to resolve these is issue you can take the following step:

  1. Disable the synchronisation and manually remove the component from the “Target” project.

  2. Manually remove the component from the Component(s) field of the effected issues

Conflicts that have to be resolved by support

The conflicts listed below need to be resolved in cooperation with our support team.

  1. “Type of source is neither Version nor ProjectComponent”

  2. “Type of target is neither Version nor ProjectComponent”

  3. “Retrieving of versions from source project = null”

  4. “Unable to determine position due to a difference in version sequence between source project and linked project”