# Transition Fields
### Correct Usage of Transition Fields in a Jira Integration
When integrating Jira with other applications, it's essential to understand the correct usage of fields to ensure data integrity and seamless workflow transitions. Transition fields in Jira are unique because they cannot be updated directly like other fields. Instead, it must be set during the ticket status transition. This document provides a thorough explanation and step-by-step instructions on properly using these fields in integrations.
#### Why Transition Fields Should Not Be Included in Field Mapping
1. **Direct Updates Not Allowed:**
* Transition fields — such as status changes, workflow triggers, or resolution updates — cannot be updated directly like standard fields. Attempting to do so often results in errors, ignored updates, or broken workflows, especially when platform-specific conditions (like required screens or validators) are not met.
2. **Workflow Integrity:**
* Mapping transition fields as regular fields disrupts the intended workflow logic. These fields are designed to trigger actions, not store static data. Treating them as mappable fields can lead to:
* Incorrect status changes.
* Skipped automation rules.
* Conflicts with validation or post-functions.
3. **Correct Transition Handling:**
* Transition fields must be handled through the status tab. This ensures:
* Workflow conditions and validators are respected.
* Status changes occur in the correct sequence.
* Related fields (like resolution) are updated consistently.
#### Correct Placement of the Resolution Field in the Integration
Instead of including the Resolution field in the **Field Mapping** section, it should be included in the **Status option**. This ensures that the field is updated during the correct status transition of the Jira ticket.
#### How to Set Up Transition Fields in Getint
**Step 1: Access the Status Tab**
* Navigate to your integration settings and open the issue type where you want to add the status transition. Then, switch to the Status tab.
**Step 2: Open the Status Configuration**
* Find the status where the transition should take place (i.e., **Done**). Click the gear icon next to it to open its configuration settings.
**Step 3: Map the Transition Fields**
* The transition fields tab will appear. Map the transition field (for example, the **Resolution**), and then select the settings icon in the resolution to open the option to match fields to configure the transitions. This ensures that the field will be set during the appropriate status transition of the Jira ticket.
**Step 4: Match the Resolutions**
* Map the options for this field just like you would for any other dropdown field, such as Assignee or Reporter.
**Step 5: Save and Validate the Configuration**
* **Save Settings:**
* Save the integration settings once all configurations are complete.
* **Validate Integration:**
* Perform a test to ensure the Resolution field is set correctly during the ticket status transitions. Create a test ticket, transition it through the configured statuses, and verify the Resolution field is updated as expected.
If you require additional assistance, don't hesitate to get in touch with our support team at our [Help Center.](https://getint.io/help-center)
---
# Agent Instructions: 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:
```
GET https://docs.getint.io/getintio-platform/workflows/transition-fields.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.