# Type Mapping

### Work Item Type Mapping in Getint <a href="#work-item-type-mapping-in-getint" id="work-item-type-mapping-in-getint"></a>

When setting up your integration, you must define the synchronization logic between work item types. Since platforms like Jira, Azure DevOps, and ServiceNow use different structures, Getint allows you to map these types specifically.

### Key Features <a href="#key-features" id="key-features"></a>

* **Directional Logic**: Specify which item type to create based on the source (for example, a Jira Task creating an Azure DevOps Bug).
* **Mapping Flexibility**: Configure individual mappings to handle corner cases, ensuring the same work item type can sync differently depending on the source.
* **Workflow Consistency**: Manage unique fields and status transitions for each type to maintain data integrity across systems.

<figure><img src="/files/LEe4XeeH0tw1eHiEtF9S" alt=""><figcaption><p>Example of type mapping, where Jira has Task mapped twice to cover specific corner cases.</p></figcaption></figure>

### Type Mapping Configurations <a href="#type-mapping-configurations" id="type-mapping-configurations"></a>

For every Type Mapping you can configure:

#### 1. Fields <a href="#id-1.-fields" id="id-1.-fields"></a>

* Map fields 1 to 1 from both mapped work item types. If one of your work item types has specific fields that are not shared across the other work item types, you can map a fixed value to these fields, or create a custom field counterpart on the other software to track this field data accordingly.

<figure><img src="/files/ZZQhagO2pNEq8obTmLn0" alt=""><figcaption><p>Left-hand side fields are from Jira, right-hand side fields are from Azure DevOps.</p></figcaption></figure>

#### 2. Status Transition <a href="#id-2.-status-transition" id="id-2.-status-transition"></a>

* If one of your work item types has a specific status transition, you can map transition fields for that specific work item mapping so that the status is synchronized accordingly.\
  One example where status transition mapping may take place is when you have transition fields for your Jira status workflow:

<figure><img src="/files/OtPbd5M501afnWcfpzE1" alt=""><figcaption><p>In the above example, updating a Jira task status from In Progress to Done will trigger a transition screen, where specific information must be filled before actually updating the status.</p></figcaption></figure>

* Status transition for type mapping can be configured on the **STATUS** tab:

<figure><img src="/files/SBRPBVYU6aMBfxnEIBBb" alt=""><figcaption></figcaption></figure>

* To make sure that status can be synced, please map available status options between both apps (each app can use different statuses, and that's why Getint requires mapped options to know what status to set when syncing an item to the other app):

<figure><img src="/files/3sHL3pytoxilrDRsfHS0" alt=""><figcaption></figcaption></figure>

* Once you map status options together, they will appear on a list.
* You can click the **trash** icon to delete a mapping or the **cog** icon to configure transition fields:

<figure><img src="/files/78GOB7uSiu5S61eCF356" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
We have an in-depth guide about transition fields and how to fully configure them here: [Transition Fields | Getint: Where every ticket finds it's place.](https://docs.getint.io/getintio-platform/workflows/transition-fields)
{% endhint %}

#### 3. Comments <a href="#id-3.-comments" id="id-3.-comments"></a>

* You can configure the synchronization logic of each mapped work item type through the **Comments & Attachments** tab (depending on the connector, it might be displayed only as Comments if attachments aren't supported):

<figure><img src="/files/05L4YVbF0804vx1sNjAp" alt=""><figcaption><p>Comments synchronization settings for Task to Task type mapping.</p></figcaption></figure>

#### 4. Attachments <a href="#id-4.-attachments" id="id-4.-attachments"></a>

* If supported by your connector, you can also configure the synchronization logic for attachments of your mapped work item types through the **Comments & Attachments** tab:

<figure><img src="/files/OIQyAg1CssdA5e0c12NB" alt=""><figcaption><p>Scroll down the "Comments &#x26; Attachments“ screen to visualize the Synchronize Attachments setting.</p></figcaption></figure>

* You can then configure the Comments synchronization settings for that specific item type mapping:

<figure><img src="/files/hiiQeC93DtLjtt46Rn0d" alt=""><figcaption></figcaption></figure>

#### 5. Hierarchy <a href="#id-5.-hierarchy" id="id-5.-hierarchy"></a>

This feature is available for mostly all type mappings when building an integration. However, it is important to note that not all apps support hierarchy in the same way as Jira, Asana, Monday, or Azure DevOps, to name a few.

At its core, it revolves around different types of issues, such as:

* **Epics**: Represent high-level initiatives or large work items.
* **Stories/Tasks**: Individual units of work that contribute to an epic.
* **Subtasks**: Manageable tasks required to complete a story.

For example, this would be the standard hierarchy levels in a Jira to Jira integration.

To enable Hierarchy settings for your mapped work item types, go to your integration and open the corresponding type mapping. For stories/tasks/bugs that you would like to sync the Epic link, you’ll need to go to **Hierarchy** > enable **Synchronize Epic relationship** > display the dropdown and select the **Parent Link (NextGen projects)**.

<figure><img src="/files/CzvuQovQuAYhA01RezNb" alt=""><figcaption></figcaption></figure>

For subtasks, open the corresponding type mapping > enable the **Synchronize Subtasks relationship** > display the dropdown, and select the **Parent Link**.

<figure><img src="/files/YsmDsdvDJGMgbLhQ7kGx" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
We have an in-depth guide about Hierarchy settings and configuration here: [Hierarchy | Getint: Where every ticket finds it's place.](https://docs.getint.io/getintio-platform/workflows/hierarchy)
{% endhint %}

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)

<figure><img src="/files/otyodSR2k1YTwh3mrnVq" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team
">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>


---

# 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/type-mapping.md?ask=<question>
```

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.