---
title: "How to troubleshoot 'Failed to push to Jira!' error message"
canonical: "https://support.appfire.com/space/CSFJIRA/3103784975/How%20to%20troubleshoot%20'Failed%20to%20push%20to%20Jira!'%20error%20message"
format: markdown
---
> Macro (aura-html)

## Summary

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

![image](media://e8d43823-2357-4fa8-a5f7-1b22d6c46bf0)

## Environment

- Jira Cloud/Server
- Any

## Diagnostics Steps

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:

<details>
<summary>"Field 'status' cannot be set. It is not on the appropriate screen, or unknown."</summary>

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

<details>
<summary>"Field 'customfield_10112' cannot be set. It is not on the appropriate screen, or unknown."</summary>

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.
</details>

<details>
<summary>"Option id 'null' is not valid"</summary>

This might be due to mapping incompatible field types. For example, having Jira <span style="color: #172b4d">'Select List (single choice)' field type mapped with Salesforce 'Picklist(Multi)' field type. </span>
</details>

<details>
<summary>"Option value 'Child 1' is not valid"</summary>

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

## Resolution

<details>
<summary>"Field 'status' cannot be set. It is not on the appropriate screen, or unknown."</summary>

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:
</details>

<details>
<summary>"Field 'customfield_10112' cannot be set. It is not on the appropriate screen, or unknown."</summary>

1. Find the custom field mentioned in the error message:
  1. In Jira, navigate to <span style="color: #172b4d">**Issues**</span><span style="color: #172b4d"> > </span><span style="color: #172b4d">**Custom fields.**</span>
  2. Click on the **Configure** for any the custom fields you have.
  3. You should see the following in the Browser URL:
  4. Change `15800` to the ID you see in the error message (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.
  5. Add the field that you have located in the previous step.
</details>

<details>
<summary>"Option id 'null' is not valid"</summary>

This might be due to the mapped field being incompatible. Check [Jira Field Type to Salesforce Field Type compatibility](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1522369149) to learn more about Jira Field Type to Salesforce Field Type compatibility.
</details>

<details>
<summary>"Option value 'Child 1' is not valid"</summary>

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](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1854180614), *Part 3: Configuring Value Mappings.*
</details>


> ℹ️ The error message is not listed here? Please [contact Technical Support](https://appfire.atlassian.net/servicedesk/customer/portals) for further assistance.