×

You're using an outdated browser

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

Manual

Component(s) not valid

Matthias Gaiser

Matthias Gaiser Last update: Mar 16, 2017

Symptoms

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

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

Cause

A Component was set to the issue in the sender project and is mapped to a value which is not a valid Component 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 components configuration of the receiving project if all components are configured the desired way.
  2. Access the Field Mappings configuration, edit the component field mapping and check that your components are mapped correctly. If you use the Passthrough Mapping, you may want to check the "create missing components" option so that Backbone will create the missing components on the fly.
    If you use the Passthrough Mapping and your component names are different in the two projects, please use the Components Mapping and map the desired components 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.

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