Version(s) not valid

Symptoms

An issue does not get synchronized and appears in the troubleshooting section with the category 'Version(s) not valid' and the message, e.g. '"versions":"Version name 'V3' is not valid"'.

The 'versions' part identifies the internal id of the field which is affected.

Cause

A version was set to the issue in the sender project and is mapped to a value which is not a valid version in the receiver project. This can be due to an invalid mapping configuration in Backbone or a missing configuration in the receiving project.

Resolution

The following steps should be done in order to resolve this problem.

1. Check the versions configuration of the receiving project if all versions are configured the desired way.
2. Access the Field Mappings configuration, edit the version field mapping and check that your versions are mapped correctly. If you use the Passthrough Mapping and your version names are different in the two projects, please go to the Project Mapping and select at least "Field mapping - missing versions created" to create missing versions automatically or use the Correlation Mapping and map the desired versions to each other.
3. After fixing your configuration...
   • ... please perform a retry if you have only changed your JIRA or backbone configuration on the receiver project.
   • ... please perform a resync if you have done changes on the sender project.