Versions Compared

Old Version 13

changes.mady.by.user Subatra Dewi Veeriah

Saved on

compared with

New Version Current

changes.mady.by.user Jeff Gleeson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

'Failed to push to Jira' error message prompts when pushing updates manually from Salesforce to Jira. 

...

Web requests can provide the full error message for further troubleshooting.

Causes

'Failed to push to Jira' error message can be caused by various issues. Below are the possible error messages you might find in the browser web requests:

...

Expand
title"Field 'status' cannot be set. It is not on the appropriate screen, or unknown."

  1. Go to Jira, Apps > Salesforce > Bindings > Mapping > Mappings

  2. Locate Status field mapping 

  3. Make the sync direction pointing to Salesforce only (Outbound sync) as shown as the picture below:

    Image RemovedImage Added
Expand
title"Field 'customfield_10112' cannot be set. It is not on the appropriate screen, or unknown."

  1. Find the custom field mentioned in the error message:

    1. In Jira, navigate to Issues > Custom fields.

    2. Click on the Configure for any the custom fields you have.

    3. You should see the following in the Browser URL:

      Code Block
      https:JIRAurl/secure/admin/EditCustomField!default.jspa?id=15800

    4. Change '15800' to the ID you see in the error message (i.e '10112'for example, 10112)

    5. Press 'Enter'.

  2. After locating the custom field name from the step above. We need to add the field to the Edit Issue screen

    1. In Jira, go to Projects > <your project>.

    2. Project Settings > Screens.

    3. Locate the Issue type and expand it.

    4. Click on the screen on the Edit issue operation.

      Image RemovedImage Added

    5. Add the field that you have located in the previous step.

Expand
title"Option id 'null' is not valid"

This might be due to the mapped field being incompatible. Check Jira Field Type to Salesforce Field Type compatibility to learn more about Jira Field Type to Salesforce Field Type compatibility. 

Expand
title"Option value 'Child 1' is not valid"

There are two solutions to this issue:

  1. Make sure that the values of the Jira and Salesforce fields are identical.

  2. Configuring value mappings to non-identical value. Please refer to Configuring Entity Mappings and Field Mappings, Part 3: Configuring Value Mappings.

Info

The error message is not listed here? Please contact Technical Support for further assistance.