> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/support-legal-and-others/troubleshooting-guide-for-getint-users/error-field-less-than-field-name-greater-than-cannot-be-set.-it-is-not-on-the-appropriate-screen-or.md).

# Error: Field '\<field-name>' cannot be set. It is not on the appropriate screen, or unknown

**Issue**: Field '\<field-name>' cannot be set. It is not on the appropriate screen, or unknown

**Description**: This error message will be displayed if the field in not available in the appropriate screen on **Jira**. For example, when a new ticket is being created in Jira from another App (during Sync), the mapped field should be available in the create screen on Jira. If the value is not available, the error message will be displayed

**Solution**:

There are 2 possible solutions

1. Add the relevant field to the appropriate screen. In the example above, the field should be added to the Create screen in Jira. Jira/Project adminstrators should be able to do this. Below link provides a detailed link to add default/custom fields to a Jira Screen\
   [![](https://wac-cdn.atlassian.com/assets/img/favicons/atlassian/favicon.png)Add, edit, and delete a field configuration | Atlassian Support](https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-a-field-configuration/)
2. Uncheck the field from ‘On Create’ and/or ‘On Update’ (if the field is not on the edit screen) in Getint mappings screen as follows

<br>

<figure><img src="https://4106311246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MR6Z9V8zLATPQPOGSDf%2Fuploads%2FdD9RW3Lmo5WGrOiNM391%2Ferror%20field%20name%20cannot%20be%20set.png?alt=media&amp;token=95b0470f-6992-4728-b681-64229a060efd" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getint.io/support-legal-and-others/troubleshooting-guide-for-getint-users/error-field-less-than-field-name-greater-than-cannot-be-set.-it-is-not-on-the-appropriate-screen-or.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.