×

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

Field not on the Screen

Matthias Gaiser

Matthias Gaiser Last update: Mar 13, 2019

Symptoms

An issue does not get synchronized and appears in the troubleshooting section with the category 'Field not on screen' and a message containing, e.g. '"customfield_11200":"Field 'customfield_11200' cannot be set. It is not on the appropriate screen, or unknown."'.

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

Cause

A change occurred in the sender project and the field which is being sent to the receiver project is not on the corresponding edit screen or transition screen (if a transition is configured for performing the changes).

Resolution

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

  1. Check if the field is defined for the corresponding screen of this project.
  2. Alternatively use the JIRA admin helper to identify the problem.
  3. Access the Field Mappings configuration and make sure that you chose the right fields for your configuration.
  4. 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

$home.properties.onThisPageHeading

    $home.properties.relatedContentHeading

    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