How to troubleshoot 'Failed to push to Jira!' error message

Jira Status field is a Read-Only field. Therefore, only outbound sync (Jira > Salesforce) is supported.

As the error suggests, the custom field with ID '10112' is not on the appropriate screen. Specifically, the custom field is not on the Edit Issue screen. 

The connector uses the mapped fields on the Jira Edit Issue screen to push updates from Salesforce to Jira. 

This might be due to mapping incompatible field types. For example, having Jira 'Select List (single choice)' field type mapped with Salesforce 'Picklist(Multi)' field type. 

The mapped fields are compatible with one another. However, the value 'Child 1' is unavailable in Jira. 

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:
   

   

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:
      
      

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

      
      

   4. Change '15800' to the ID you see in the error message (i.e '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
      

      

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

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. 

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.