> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-ticketing/custom-field-mapping.md).
# Map custom fields for Jira, JSM and Zendesk
Map Siit request fields such as status, priority and category to custom fields in Jira, JSM and Zendesk so requests sync or escalate to those tools without losing data
#### Why does custom field mapping matter?
In many organizations, IT and Operations teams work across multiple tools: Siit for internal request handling, Jira or JSM for Engineering or Product teams, Zendesk for Customer Support, and so on.
When a request created in Siit needs to be **synced or escalated to one of these external platforms**, it’s critical that the information is **mapped accurately** — so no data is lost, misrouted, or misunderstood.
That’s where **Custom Field Mapping** comes in.
#### What you can do with custom field mapping?
Siit’s **Custom Field Mapping** feature gives you **full control** over how requests are sent to and synced with external platforms like **Jira**, **JSM**, and **Zendesk**.
With it, you can:
* **Align your internal request fields** (e.g. status, priority, category) with **custom fields** on the destination tool
* **Route specific request types** or values to the right queue, form, or team
* Ensure that **external teams** receive the **right level of context** to take over the request seamlessly
It helps eliminate friction and prevents miscommunication between teams — especially when different tools are used for internal and external workflows.
#### How to set it up in your integration settings
To configure custom field mapping:
1. Go to your **Integrations** **Library** and select the integration (e.g. Jira, Zendesk)
2. Click **Settings**
3. ```
Navigate to the **Field Mapping** section.
```
4. ```
For each Siit field you want to map:
```
* * Choose a **Siit source value**:
* Standard values like **Status**, **Priority**, **Request ID**, etc.
* Or custom values from the **Service Catalog** (i.e. specific form questions and answers)
5. ```
Match it to the corresponding **custom field** in the external tool.
```
6. ```
Save and test the configuration to ensure correct data transfer.
```
**⚠️ Note:** The JSM Customer Request Type is no longer mapped here. It has its own picker under *Settings → Integrations → Jira → Jira settings*. See the \[[Jira setup guide](/guides/integrations/integrations-ticketing/jira-guide.md)] for details.
---
# 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.siit.io/guides/integrations/integrations-ticketing/custom-field-mapping.md?ask=&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.
