Jira Jira integration
Last updated
Was this helpful?
Last updated
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.
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 more.
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: Connection.
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.
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.
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:
Log in to your Jira Data Center instance.
Click on the Avatar at the top right of the screen.
Select Profile and then Personal Access Tokens.
Click on Create Token, provide a name for your token, and specify whether the token will expire and when.
Copy the token and store it in a safe location.
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.
Repeat the process on the other side. Since you are connecting Jira with Jira, repeat the steps.
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.
Review or manually assign the fields to integrate and synchronize within the mapped types, such as title, description, assignees, custom fields, and more.
Map assignees according to your organization’s requirements.
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.
Make sure you’re using the correct fields that represent the statuses for each Jira instance.
It is possible to filter the synchronization to have them customized for your needs and requirements.
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.
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")).
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.
Complete the integration setup by naming your project and clicking SAVE in the top right corner.
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 Help Center or Schedule a Demo. We're here to help!
