# Jira Notion integration

Getint’s Jira-Notion integration creates a unified workspace by syncing project data across platforms. Currently supporting title and description fields—with more mapping options on the roadmap—the integration is designed for rapid deployment via a **3-minute MVP setup**. To bridge any current feature gaps, Getint provides expert support, including **custom scripts and personalized onboarding**, to help teams navigate complex workflows.

<figure><img src="/files/XGRVRtUuoDBT3lLlcDfd" alt=""><figcaption><p><a href="https://marketplace.atlassian.com/apps/1231784/notion-integration-for-jira-two-way-notion-connector?hosting=cloud&#x26;tab=overview">Check out our Notion integration app on the Atlassian Marketplace</a></p></figcaption></figure>

***

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

The Notion-Jira licensing model with Getint is designed to accommodate different 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 seamless data synchronization between Notion and Jira.

  This makes setup simpler and faster, without the need for additional configurations in Notion.

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

* For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.

For more details on licensing, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/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.
* Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.
* **Personal Access Tokens** are required for Jira and Notion authentication. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#notion).

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

Set up your MVP integration in minutes with this step-by-step video guide.

{% embed url="<https://drive.google.com/file/u/2/d/1KX_clP-aw8RvTZTQ0t3C1RYO49TIx8eC/view>" %}

#### 1. Access the Getint 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 Jira Notion integration app.

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

* Select **Create Integration**, then **Continuous Sync** or **Migration** based on your requirements.

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

#### 2. Token Generation (Password for Jira Cloud) <a href="#id-2.-token-generation-password-for-jira-cloud" id="id-2.-token-generation-password-for-jira-cloud"></a>

* For Jira Cloud, generate a Jira token. This token will act as your password:
  * Go to **Atlassian Account Settings**.
  * Navigate to **Security** and go to **Generate and manage** **API tokens**, then select an API token or an API token with scopes.
  * After creation, use this token as the password for Jira integration. More information about access tokens for Jira [here](https://docs.getint.io/guides/quickstart/connection#jira).

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

#### 3. Generate a Notion Personal Access Token <a href="#id-3.-generate-a-notion-personal-access-token" id="id-3.-generate-a-notion-personal-access-token"></a>

* Click the **ellipsis** (···) in the top-right corner of your Notion app.
* Select **Add a Connection** > **Manage Connections** > **Develop or Manage integrations**.
* Click **+ New Integration**, give it a name, and configure your permissions.
* Secure your **Internal Integration Secret** (API token) for the next step.
* Under **Content Access**, ensure you select the specific teamspace containing the project you want to sync.

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

* Make sure to securely store your token, as it will only be visible once.

#### 4. Connect to Jira <a href="#id-4.-connect-to-jira" id="id-4.-connect-to-jira"></a>

* In Getint, click on **Connect App** and choose Jira.
* Enter your Jira instance URL, username, and the API token.
* Use the Personal Access Token for Jira Cloud.

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

* Select the Jira project you wish to integrate with Notion.

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

{% hint style="warning" %}
You can only select one project when syncing with Notion. Selecting multiple projects will cause Notion to disappear from your available integration options.
{% endhint %}

#### 5. Configure Getint for Notion <a href="#id-5.-configure-getint-for-notion" id="id-5.-configure-getint-for-notion"></a>

* In the Getint app, choose **Notion** as the connection app.
* Select **Create a new connection**, name it, and provide the **API Token**.
* Select the connection you want to integrate.
* Choose the Notion database to synchronize.

{% embed url="<https://drive.google.com/file/d/1urjT4T9TyWJRHYzdvra4EghZYqrR97LF/view>" %}

#### 6. Map Types <a href="#id-6.-map-types" id="id-6.-map-types"></a>

* Link Jira types (Task, Bug, Epic, Story) to synchronize with Notion.
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process.
* **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 (Task, Bug, Epic, Story) yourself.
  * For example, **Task ↔ Task**.

{% embed url="<https://drive.google.com/file/d/1oC0W2g2tEZ8vyt8k-y8Rh26-cHQ0eFdc/view>" %}

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

* Map key fields such as **Title**, **Description**, **Assignees**, and **Custom** fields.
* You can use the arrows to distinguish the sync direction of the fields.
* Once your fields and types are configured, assign a unique name to your integration and save your settings.

{% embed url="<https://drive.google.com/file/d/12Id4mx16AjtSDOQwwOy9vXkKSjC-TsLx/view>" %}

{% hint style="warning" %}
The **Description** field in Notion supports a maximum of 2000 characters. To avoid sync errors and blank description fields when transferring text from Jira to Notion, ensure your content does not exceed this limit. Keeping descriptions concise and within the character count helps maintain data integrity and prevents synchronization issues.
{% endhint %}

#### 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 Notion 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/NduS5FHisD8Jm1H97UZj" 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 Notion. For example, **To do** in Jira could be mapped to **Open** in Notion.

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

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

Check the **Comments** 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 in either Jira or Notion will reflect in the other platform.
* **Unidirectional to Jira**: Data flows exclusively from Notion to Jira. Changes made in Jira will not sync back to Notion.
* **Unidirectional to Notion**: Data flows exclusively from Jira to Notion. Changes made in Notion 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 entirely. This prevents any data transfer for these specific fields while keeping other mapped fields active.

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

{% hint style="warning" %}
Attachment syncing is currently not supported for Notion integrations.
{% endhint %}

#### 11. Filtering <a href="#id-11.-filtering" id="id-11.-filtering"></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.
* 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).

{% embed url="<https://drive.google.com/file/d/1iVwA8O1-n0u_z-2zBErkxguIWZA7z2lj/view>" %}

**JQL Filtering:**&#x20;

* 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.

{% embed url="<https://drive.google.com/file/d/18k1sDqD7hOlAFtymz3RkAEeQX7LHeRUX/view>" %}

#### 12. Duplicate Setup and Select Different Projects <a href="#id-12.-duplicate-setup-and-select-different-projects" id="id-12.-duplicate-setup-and-select-different-projects"></a>

* Go to **Workflows**.
* Click on the 3 dots on the right side and select **duplicate**.
* A side panel will appear. Select a new name for the integration (by default, the integration will be called **copy of** if the same projects are established).
* In the dropdown menu, select the projects that you would like to integrate.
* For each side, select **Connect**. Then **Duplicate**.
* Save the new integration.

{% embed url="<https://drive.google.com/file/d/1oIcXh_0_PZXAPbfvLZZJn8zcm8Bu6w4o/view>" %}

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

By following these steps, you have established a functional integration between **Jira** and **Notion**. 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-notion-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.