×

You're using an outdated browser

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

$home.properties.pagetreeHeading.asText

Security level name is not valid

Sebastian Hesse

Sebastian Hesse Last update: Jul 30, 2019

Symptoms

An issue does not get synchronized and appears in the troubleshooting section with the category 'Security level name is not valid' and the message, e.g. '"security":"Security level name 'internal' is not valid"'.

The 'security' part identifies the name of the field which is affected.

Cause

A security level was set to the issue in the sender project and is mapped to a value which is not a valid security level 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 security configuration of the receiving project if all security level are configured the desired way.
  2. Access the Field Mappings configuration, edit the security level field mapping and check that your security levels are mapped correctly. If you use the Passthrough Mapping and your security level names are different in the two projects, please rename the security levels in order to match or use the Security Level Correlation Mapping and map the desired security levels 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.

References

Please also have a look to our field mapping documentation for the  Security level.

2x$versions.current.name
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