# Jira Freshservice integration

The Getint platform links Jira and Freshservice to unify project management and IT service management (ITSM). It supports fast ticket syncing, automated workflows, and shared dashboards, cutting response times by up to 40%. Follow our 2026 guide for quick setup across all business sizes. Use Jira-Freshservice integration with Getint for better project and support management.

<figure><img src="/files/1fDdSWJvNGbFLniQh4Ix" alt=""><figcaption><p><a href="https://marketplace.atlassian.com/apps/1227929/freshservice-freshdesk-integration-for-jira-2-way-work-sync?hosting=cloud&#x26;tab=overview">Check out our Freshservice integration app on the Atlassian Marketplace</a></p></figcaption></figure>

***

### Jira-Freshservice Licensing Model <a href="#jira-freshservice-licensing-model" id="jira-freshservice-licensing-model"></a>

The **Freshservice-Jira licensing model** with Getint fits various integration needs. Here’s an overview:

#### Standard Licensing <a href="#standard-licensing" id="standard-licensing"></a>

* A Getint license is required only on Jira, enabling data synchronization between Freshservice and Jira.
* This keeps setup simple and quick, with no extra configurations needed in Freshservice.

#### Flexible License <a href="#flexible-license" id="flexible-license"></a>

* For managed services companies or organizations integrating four or more instances (same or different tools), Getint provides a **Flexible License**. This custom option covers a set number of connections (up to 10 instances) without tool limits. You can switch integrated tools anytime during the license term for maximum adaptability.

For licensing details, visit our [**Pricing Page**](https://docs.getint.io/licensing).

#### Requirements to Build Your Integration <a href="#requirements-to-build-your-integration" id="requirements-to-build-your-integration"></a>

* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated **Service Accounts** for both instances. Create a Service Account here: [How to Create a Jira Service Account](https://docs.getint.io/getting-started-with-the-platform/preparing-for-the-integration#how-to-create-a-jira-service-account).
* **Personal Access Tokens** are required for Jira and Freshservice authentication. Learn more here: [Access Tokens](https://docs.getint.io/guides/quickstart/connection#jira).

### Setting Up Your Jira-Freshservice Integration <a href="#setting-up-your-jira-freshservice-integration" id="setting-up-your-jira-freshservice-integration"></a>

#### 1. Access the [Getint](https://marketplace.atlassian.com/apps/1227929/freshservice-freshdesk-integration-for-jira-2-way-work-sync?hosting=cloud\&tab=installation) App in Jira: <a href="#id-1.-access-the-getint-app-in-jira" id="id-1.-access-the-getint-app-in-jira"></a>

* Navigate to Jira, go to Apps, and select the Getint app (Freshdesk/Freshservice integration for Jira in this case).

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

#### 2. Create Integration <a href="#id-2.-create-integration" id="id-2.-create-integration"></a>

Click **Create Integration** and select either:

* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.

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

#### 3. Generate a Jira API Token <a href="#id-3.-generate-a-jira-api-token" id="id-3.-generate-a-jira-api-token"></a>

* Log in to your Atlassian account and navigate to **Account Settings** > **Security** > **API Tokens** **> Create and manage API tokens**.

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

* Choose between **Create API token** and **Create API token with scopes**. Generate the token, copy it, and securely store the token, as it will be used as the password for Jira Cloud.

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

{% hint style="info" %}
For detailed steps and specific permissions for the Jira user, refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#jira).
{% endhint %}

#### 4. Generate a Freshservice Personal Access Token <a href="#id-4.-generate-a-freshservice-personal-access-token" id="id-4.-generate-a-freshservice-personal-access-token"></a>

* Log in to your Freshservice account, click on your profile picture in the top right corner, and select **Profile Settings**.
* On the new page, click on **Show API Key** to access the API key.
* Complete the captcha verification, if prompted, and copy the API Key for integration.

{% embed url="<https://www.loom.com/share/191e48840a6c44e787d219cbb5893d7d>" %}

{% hint style="info" %}
You can reset the API Key to stop an app from connecting to your helpdesk if you need to. Remember that doing so will also disconnect other apps that use the same key.
{% endhint %}

#### 5. Create a Connection with Jira and Freshservice <a href="#id-5.-create-a-connection-with-jira-and-freshservice" id="id-5.-create-a-connection-with-jira-and-freshservice"></a>

**Jira Connection:**

* Select the **Jira** app. Then enter your Jira instance **URL**, username, the Access token generated, and click **Add**.

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

* Select the Jira project(s) you want to synchronize and select **Connect**.

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

**Freshservice Connection:**

* Select **Freshservice** as the connection app, and click **Create New Connection**.

<figure><img src="/files/7k5xx77JbeqNX0LEDcvI" alt=""><figcaption></figcaption></figure>

* Enter your Freshservice instance URL in the **URL** field and click **Next**.

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

* Assign a name to the connection and enter the API token.

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

* **Add** the connection and select it.

{% hint style="info" %}
For detailed steps on how to configure your **Freshservice API token**, please refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#freshservice).
{% endhint %}

#### 6. Configure Type Mapping <a href="#id-6.-configure-type-mapping" id="id-6.-configure-type-mapping"></a>

* **Quick Build**: Use the Quick Build feature to automatically map fields and types between applications, simplifying the process.

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

* **Manual Mapping**: For greater control, manually map the types yourself. This approach lets you tailor the mapping to meet your specific needs. Click **+ Add type mapping** to add the types (Incident, Task, Bug, Epic, Story) by yourself.
  * For example, **Task ↔ Service Request**.

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

#### **7. Configure Field Mapping** <a href="#id-7.-configure-field-mapping" id="id-7.-configure-field-mapping"></a>

Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields. In addition to this, for the Freshservice connection to work, it is necessary to map some key fields:

1. **Reporter/Requester Mapping**:
   * Link the **Reporter** field in Jira to the **Requester** field in Freshservice.
   * Ensure that requesters on both platforms are mapped to allow Getint to match them appropriately.
     * In case a fixed value, like an email, is supposed to be defined for this field, the configuration can be done like this:
2. **Status Field**:
   * Freshservice mandates status mapping for the integration to function. A default value needs to be set for the ticket creation only, pointing towards the Freshservice side, avoiding this option being picked up again when the issues are updated:
3. **Priority Field**:
   * Mapping the priority field is necessary for the integration's operation within Freshservice.

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

* After all fields and types have been configured, give your integration a distinctive name and save the settings.

&#x20;

#### 8. Assignee Mapping <a href="#id-8.-assignee-mapping" id="id-8.-assignee-mapping"></a>

Use the assignee mapping option to match Jira assignees to Freshservice assignees, enabling precise synchronization of task ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).

<figure><img src="/files/7M3ZvqsnIjzoHemWAPJs" alt=""><figcaption></figcaption></figure>

#### 9. Status Mapping <a href="#id-9.-status-mapping" id="id-9.-status-mapping"></a>

Map status fields to align between Jira and Freshservice. For example, **To do** in Jira could be mapped to **Open** in Freshservice.

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

#### 10. How to Manage Comments & Attachments: <a href="#id-10.-how-to-manage-comments-and-attachments" id="id-10.-how-to-manage-comments-and-attachments"></a>

Check the **Comments & Attachments** tab. These settings are active by default, but you can modify them to fit your specific requirements.

**Synchronization Directions**

The platform supports three distinct logic flows for these items:

* **Bidirectional**: Updates to comments or attachments in either Jira or Freshservice will reflect in the other platform.
* **Unidirectional to Jira**: Data flows exclusively from Freshservice to Jira. Changes made in Jira will not sync back to Freshservice.
* **Unidirectional to Freshservice**: Data flows exclusively from Jira to Freshservice. Changes made in Freshservice will not sync back to Jira.

**Disabling Sync**

If your organization has strict data privacy policies or if these items are not relevant to a specific integration, you can **disable** comments and attachments entirely. This prevents any data transfer for these specific fields while keeping other mapped fields active.

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

#### 11. Filtering Options <a href="#id-11.-filtering-options" id="id-11.-filtering-options"></a>

Customize synchronization by applying filters:

* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.

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

* Choose the filter scope:
  * **ALL items filter**: Rules will be verified for every item before synchronization.
  * **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
  * **SYNCED items filter**: Rules will be verified for items that were already synced in the past.

Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).

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

**JQL Filtering (Jira-Specific)**

Beyond standard item filtering, integrations involving Jira support **Jira Query Language (JQL)**. This allows for granular control over exactly which issues enter the synchronization scope.

**Custom JQL Configuration**

In the **Custom JQL** field, you can input a specific query to refine your data set. The platform automatically appends your custom string to the system-generated filters.

* **Logic:** The final query used to identify issues is effectively `(System Filters) AND (Your Custom JQL)`.
* **Example:** If you only want to sync issues currently being worked on, you would enter:

  `status IN ("In Progress")`

**Key Benefits**

* **Precision**: Target specific issue types, labels, or custom field values that standard UI filters might not cover.
* **Performance**: By narrowing the scope of the sync via JQL, you reduce the volume of data the platform needs to scan, often resulting in faster processing.
* **Flexibility**: Use advanced operators (e.g., `WAS`, `CHANGED`, `is EMPTY`) to handle complex workflow requirements.

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

#### 12. Test the Integration <a href="#id-12.-test-the-integration" id="id-12.-test-the-integration"></a>

Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between **Freshservice** and **Jira**.

**Verification Steps**

1. **Initial Creation:**
   * Create a test ticket in **Freshservice**.
   * Create a test issue in **Jira**.
   * Confirm that the items appear in the respective platforms according to your mapping rules.
2. **Field & Feature Validation:**
   * **Updates**: Modify a mapped field and confirm the change reflects on the linked platform.
   * **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
   * **Status Transitions**: Change the status (e.g., move a Jira issue to "In Progress") and verify the **Freshservice** ticket updates accordingly.
3. **Audit Logs:**
   * Access the **Logs** tab within the platform.
   * Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.

***

### Conclusion <a href="#conclusion" id="conclusion"></a>

By following these steps, you have established a functional integration between **Jira** and **Freshservice**. This setup automates the synchronization of records, workflows, and communication, bridging the gap between support and development teams.

For further assistance, please contact us at the [Support Center](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).

<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/guides/integration-synchronization/jira-freshservice-integration.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.