> For the complete documentation index, see [llms.txt](https://docs.mybytes.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mybytes.tech/zoho-desk/jira-connector-for-zoho-desk/user-guide/review-fields.md).

# Review Fields

The fields shown in the **Review Fields** are rendered based on your **Jira project's Create Issue screen**. 

{% hint style="info" %}
To manage which fields appear on the Create Issue screen, refer to Atlassian’s guide:  [Manage screen schemes](https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/)
{% endhint %}

#### ✅ Currently Supported Fields:

We currently support the following field types:

* **Summary** (Text)
* **Description** (Text area)
* **Priority** (Dropdown)
* **Assignee** (User picker)
* **Custom fields** – limited to the following types:
  * Single-line text
  * Multi-line text
  * Select List (Single choice)
  * Number field

#### ⚠️ Missing Fields?

* If a field configured in your Jira Create Issue screen is not shown here, it may not be supported yet.
* To request support for additional field types, please email us at **<support@mybytes.tech>** with the field name and type.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mybytes.tech/zoho-desk/jira-connector-for-zoho-desk/user-guide/review-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.