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.
Notion-Jira Licensing Model
The Notion-Jira licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:
Standard Licensing
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
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.
Requirements to Build Your Integration:
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.
Setting Up Your Notion-Jira Integration
Set up your MVP integration in minutes with this step-by-step video guide.
1. Access the Getint App in Jira:
Navigate to Jira, go to Apps, and select the Jira Notion integration app.
Select Create Integration, then Continuous Sync or Migration based on your requirements.
2. Token Generation (Password for Jira Cloud)
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.
3. Generate a Notion Personal Access Token
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.
Make sure to securely store your token, as it will only be visible once.
4. Connect to Jira
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.
Select the Jira project you wish to integrate with Notion.
You can only select one project when syncing with Notion. Selecting multiple projects will cause Notion to disappear from your available integration options.
5. Configure Getint for Notion
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.
6. Map Types
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.
7. Field Mapping
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.
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.
8. Assignee Mapping
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.
9. Status Mapping
Map status fields to align between Jira and Notion. For example, To do in Jira could be mapped to Open in Notion.
10. How to Manage Comments:
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.
Attachment syncing is currently not supported for Notion integrations.
11. Filtering
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.
JQL Filtering:
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.
12. Duplicate Setup and Select Different Projects
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.
Conclusion
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 or Schedule a Demo.
Last updated
Was this helpful?