×

You're using an outdated browser

For a better experience, keep your browser up to date. Check here for the latest version.

Manual

Option not valid

Matthias Gaiser

Matthias Gaiser Last update: Jun 17, 2016

Symptoms

An issue does not get synchronized and appears in the troubleshooting section with the category 'Option not valid' and the message, e.g. '"customfield_10201":"Option value '1' is not valid"'.

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

Cause

An option was set to the issue in the sender project and is mapped to a value which is not a valid option 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 options configuration of the receiving project if all options are configured the desired way.
  2. Access the Field Mappings configuration, edit the corresponding options field mapping and check that your options are mapped correctly. If you use the Passthrough Mapping and your option names are different in the two projects, please use the Options Mapping and map the desired options 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.

Note

If you map cascading select fields, make sure that you...

  • ...do not select a second-level-option as default value.
  • ...do not map a first-level-option to a second-level-option
2x$versions.current.name

On this page

    Related content

    We use cookies to create a secure and effective browsing experience for our website visitors and to understand how you use our site (i.e. Google Analytics). For more information: click here.
    Ok