Getint: Where every ticket finds it's place.
Support portalCase studiesSchedule a demo
  • Welcome to the Getint Documentation Hub
  • Getting started with Getint
    • About Getint / Concepts
      • How Getint works (how it syncs the data)
      • Onboarding
      • What is a Connection?
      • What Are Runs
      • One-directional / Bi-directional integration
      • Migration vs Integration
      • How Integrations Are Executed By Getint
    • Starting the Free Trial and Accessing the Getint App
      • Selecting the Correct app per license
      • How do I extend the trial of getint.io?
      • Jira Access and User Management
    • Deployment options
      • Getint for Jira Data Center / Jira Server
        • Getint Jira Server / Jira Data Center App (native)
        • Getint for Jira Data Center / Jira Server - Architecture
      • Getint for Jira Cloud
      • Getint On-Premise
        • Architecture
        • Installation
          • How to Install Getint On-Premise in Windows Server
          • On-Premise/Standalone Guide
        • Updating On-Premise
        • Cluster High Availability
    • Prepare for the integration
      • Understanding the difference between platforms you integrate
      • One-to-One, One-to-Many, and Many-to-Many integration
      • Simplifying Workflow Sync with Getint: Jira
    • Connectors
      • Jira
      • Asana
      • Azure DevOps
      • Freshdesk
      • GitLab
      • HubSpot
      • Monday.com
      • Notion
      • Salesforce
      • ServiceNow
      • Zendesk
  • Guides
    • Quickstart
      • Integration
      • Connection
    • Integration Guides
      • How to Map Fields
      • How to create a custom field in all supported software
      • Git Repository integration
        • Git Connector - Azure DevOps
        • Git Connector - GitHub
        • Git Connector - GitLab
      • Azure DevOps Asana integration
      • Jira Airtable integration
      • Jira Asana integration
        • Jira - Asana: Subtasks synchronization
      • Jira Azure DevOps integration
        • How to Setup a Connection with Azure DevOps On-Premise
        • Jira - Azure DevOps: Epics and Subtasks Synchronization
        • Syncing Dependencies between Jira and Azure DevOps using Getint
      • Jira ClickUp integration
      • Jira Freshdesk integration
      • Jira Freshservice integration
      • Jira GitHub integration
      • Jira GitLab integration
        • Attachments Sync in GitLab Integration
      • Jira HubSpot integration
      • Jira Jira integration
        • Jira Jira licensing
        • Time Tracking in Getint – One-Way Synchronization
      • Jira Monday.com integration
        • Synchronizing Attachments in a Monday.com Integration
        • How to Insert Monday.com Items into Specific Groups Using Getint
      • Jira Notion integration
      • Jira Salesforce integration
        • Salesforce OAuth Authentication
      • Jira ServiceNow integration
        • Creating a ServiceNow User for Getint Integration
        • ServiceNow OAuth authentication
        • Creating a Custom Field in ServiceNow
        • How to Restrict "Incident" Data to Specific 3rd Party Companies
        • How to Restrict Access to Specific Tables for Integration
        • REST API requests list
      • Jira Trello integration
      • Jira Wrike integration
      • Jira Zendesk integration
        • How to Manually Provide Zendesk Organization ID and Name
    • Migration Guides
      • Migrating Data with Getint
      • Migration support, and onboarding
      • Jira to Jira migration
      • Asana to Jira migration
      • Azure DevOps to Jira migration
      • GitLab to Jira migration
      • Jira to Monday.com Migration
      • Jira Zendesk migration
  • Using Getint
    • Core Features of Getint
    • Workflows
      • Type Mapping
      • Integrations List
      • Configuring Your Data Sync: Bidirectional and Unidirectional Options
      • Syncing Attachments
      • Hierarchy
      • Assignees (users) mapping
      • Mapping Labels
      • Filtering Items for Integration in Getint
        • Troubleshooting Sync Issues: Unmet Filter Conditions
        • How to Filter Comments
        • Filtering by Assignment Group and Status
      • Shared Mappings in Getint – Centralized Mapping for Efficient Integrations
      • How to Use JQL Filters for Jira Integrations
      • Integration status
      • Storing counterpart link in the task comment
      • Storing Reference IDs/URLs Across Integrations
    • Connections
      • Troubleshooting Getint Integration Connectivity Issues
      • Permissions Issue: Status Code 500
      • Editing Connections for Existing Integrations
      • Changing the URL or Transitioning Between Instances
      • Debugging Connections in Getint: How to Troubleshoot and Resolve Issues
    • Quick Build
    • Reporting
    • Notifications
    • Request type issue on Jira Service Management how to select and work with it
    • Integrating one project with many: Streamlining synchronization across multiple projects.
      • One to Many Project - El Ride Use Case
    • Transition Fields
    • Resync and Hard Resync
    • Synchronizing Existing Items on Both Sides
    • Handling Syncs for Deleted Items
    • Advanced Scripting
    • Platform Release History
      • Getint Version 1.79
      • Getint Version 1.78
      • Getint Version 1.77
      • Getint Version 1.76
      • Getint Version 1.75
    • Settings
      • Data Storage
      • Sharing Access Permission
      • How to Override Getint Behavior Using Custom Properties
  • Support, legal & others
    • FAQ
      • Technical FAQ
      • Security FAQ
    • Troubleshooting Guide for Getint Users
      • Resolving Error 500 in Jira ServiceNow Integration
      • Locating Your Instance ID for Support
      • Connection Error: Certification Path Failed/PKIX Path Building Failed
      • Error: Field '<field-name>' cannot be set. It is not on the appropriate screen, or unknown
      • Connection timed out error
      • Troubleshooting: Integration Task Retrieval Error
      • Upgrade to newest version from version lower than 1.52
      • Debug Requests Feature
      • Troubleshooting: Resolving Hanging Integration Runs in Getint
      • Troubleshooting License Issues in Getint
    • Security and compliance
    • Support / SLA
    • Privacy & Security
      • Data Residency with Getint
    • Procurement & Legal
      • Enhanced Support for Vendor Onboarding and Security Assessments
      • EULA
      • Privacy policy
  • Billing & Services
    • Transparent and User-Friendly Pricing
    • Consulting and Custom Development
    • Understanding Getint Licensing and Pricing
      • How to pay for the apps
      • Migrations
      • Network License
      • Jira-Jira Licensing Model
      • Partners
      • Seamless Transition Offer: Migrate from Competitors to Getint with Exclusive Benefits
  • Use cases
  • Pricing Comparison: Getint vs. Alternatives
  • Battlecards (getint.io vs competitors)
  • Free migration from ConnectAll, Backbone, Exalate, Unito, Workato, TFS4JIRA and other tools
  • Anything missing? Getint is feedback driven
Powered by GitBook
On this page
  • Jira Jira Licensing Model:
  • Requirements to Build Your Integration:
  • Setting up your Jira integration

Was this helpful?

  1. Guides
  2. Integration Guides

Jira Jira integration

PreviousJira HubSpot integrationNextJira Jira licensing

Last updated 3 months ago

Was this helpful?

Integrating Jira with Jira through Getint provides users with a robust solution to streamline project management and collaboration workflows. This powerful integration enables seamless data synchronization across different projects within the same platform, allowing users to efficiently track and manage Jira tickets, tasks, bugs, and epics in diverse Jira environments. For example, a company developing various products such as mobile phones, computers, and smartwatches can benefit from this integration. While each development team operates within its designated Jira environment, Getint facilitates collaboration across projects by enabling integration and filtering of relevant projects, ensuring teams can work together effectively while maintaining appropriate access restrictions.

While some steps may vary depending on your current deployment, we support syncing items from Jira Software (Cloud and Service Management), and Jira Data Center.

Jira Jira Licensing Model:

The Jira Jira licensing model with Getint is designed to accommodate various integration scenarios. Here's a breakdown:

  • Standard Dual Licensing: This model requires the Getint license to be installed on both Jira instances involved in the integration. This ensures that each instance is properly licensed and can communicate seamlessly.

  • Remote License: For situations where installing the Getint app on both Jira instances is not feasible (e.g., when integrating with a partner company that doesn't want to install any additional apps), Getint offers a Remote License for a fixed fee. This provides a flexible solution for such cases.

  • 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 information about our licensing options, please read

Requirements to Build Your Integration:

  • The Jira Jira Getint app must be installed on both instances unless you’re opting for a Remote License (app installed on a single instance only).

  • Both Jira instances should include a dedicated user and an associated API token. These users must have permission to read, write, view, and modify the project.

  • Comments are added as the user you chose to create the connection. Therefore, we recommend using dedicated Service Accounts for both instances as comments will be attributed to the user who established the connection.

  • Personal Access Tokens to establish the connections. More information about creating API tokens here: .

Setting up your Jira integration

  • Navigate to Jira, go to Apps, and select the Getint app (Jira - Jira integration in this case).

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

2. Token Generation for Jira:

Jira Cloud

  • Sign in to your Atlassian account and navigate to the Account Settings.

  • Head to the Security section and select Personal API Token.

  • Click on Create API token and provide a label to identify your token easily.

  • Hit Create to generate the token.

  • Copy the token and store it securely in a safe location.

Jira Data Center

Unlike Jira Cloud, the Data Center does not require a token and can be accessed using an email and password. If you choose to use a token, leave the email option blank on the Getint platform:

  1. Log in to your Jira Data Center instance.

  2. Click on the Avatar at the top right of the screen.

  3. Select Profile and then Personal Access Tokens.

  4. Click on Create Token, provide a name for your token, and specify whether the token will expire and when.

  5. Copy the token and store it in a safe location.

3. Establish a Connection with Jira:

  • Ensure you're logged in as a user with the correct permissions.

  • Click Select App and choose Jira.

  • Select Create New to connect with your Jira instance.

  • Name your connection, and add the URL of your Jira instance.

  • Provide the login credentials.

4. Choose and Connect the Second Jira Project:

  • Repeat the process on the other side. Since you are connecting Jira with Jira, repeat the steps.

5. Type Mapping:

  • Quick Build (Beta): Utilize the Quick Build feature to automatically map fields and types between your applications. This feature simplifies the 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 Jira types (Task, Bug, Epic, Story) by yourself.

  • After configuring your type and field mappings, name and save your integration settings.

6. Field Mapping:

  • Review or manually assign the fields to integrate and synchronize within the mapped types, such as title, description, assignees, custom fields, and more.

7. Assignees Mapping:

  • Map assignees according to your organization’s requirements.

8. How to Manage Comments & Attachments:

  • Review the Comments & Attachments tab. These features are enabled by default, but you can adjust them as needed to suit your organization's requirements.

  • For Jira Jira integrations, you have the option to further customize comment creation under Customize comments creation. This allows you to specify whether comments should be Public, Private, or omitted entirely, providing flexibility to meet your needs.

  • You can also modify the sync direction for comments and attachments: Both ways, only to Jira A (left), or only to Jira B (right).

You can disable comments and attachments entirely if they are not needed or are restricted in your organization.

9. Mapping Statuses

  • Make sure you’re using the correct fields that represent the statuses for each Jira instance.

10. How to Enable Filters:

It is possible to filter the synchronization to have them customized for your needs and requirements.

UI Filtering

  • After finalizing your integration, you may also add filters to each Jira instance. Select the filter icon adjacent to the app icon within your integration. This action will affect the corresponding side of the integration.

  • Define Filter Rules:

    • ALL items filters: Rules will be verified for every item before synchronization.

    • NEW items filters: Rules will be verified only for newly created items that have not yet been synced.

    • SYNCED items filters: Rules will be verified for items that were already synced in the past.

JQL Filtering:

  • Select the side that will receive the filter.

  • Under the field Custom JQL, it is possible to provide a JQL, which will be the filter for your sync and appended to the one generated when searching for issues in Jira (i.e., status in ("In Progress")).

11. Duplicating Your Setup and Selecting Different Projects:

  • Go to Workflows.

  • Click 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).

  • On the dropdown menu, select the projects that you would like to integrate.

  • For each side, select Connect. Then Duplicate.

  • Save the new integration.

This setup applies to both Jira Software and Jira Service Management, enabling integration of tasks, bugs, and epics, as well as incidents, service requests, and IT help types specific to Jira Service Management.

12. Final Steps:

  • Complete the integration setup by naming your project and clicking SAVE in the top right corner.

1. Access the App in Jira:

At Getint, we're dedicated to providing exceptional support throughout your integration journey. Our team is committed to delivering the best customer experience. For any questions about this integration or assistance with the setup process, don't hesitate to open a ticket at our or . We're here to help!

Getint
Help Center
Schedule a Demo
more.
Connection
Example of automatic field mappings with Quick Build where you can also add fields manually while using this feature.
For more information about this feature, please visit
Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!
Items Filtering.
Having issues to build your integration? Schedule a free consultation with our Integration Experts now!