Jira Jira integration
Integrating Jira with Jira through Getint gives teams a reliable way to connect project management and collaboration workflows. The integration synchronizes data across different projects on the same platform, so users can track and manage Jira tickets, tasks, bugs, and epics across multiple Jira environments.
For example, a company building several products, such as mobile phones, computers, and smartwatches, can put this to use. Each development team works within its own Jira environment, while Getint connects them by integrating and filtering the relevant projects. Teams collaborate effectively, and access restrictions stay in place.
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 more.
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 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.
Personal Access Tokens to establish the connections. More information about creating API tokens here: Access Tokens & Requirements | Getint: Where every ticket finds it's place.
Setting Up Your Jira Integration
1. Access the Getint App in Jira:
Navigate to Jira, go to Apps, and select the Getint app (Jira - Jira integration in this case).
2. Create Integration
Click Create Integration and select either:
Continuous Sync for ongoing synchronization.
Migration for a one-time data transfer.
3. Generate a Jira Cloud API Token
Log in to your Atlassian account and navigate to Account Settings > Security > API Tokens > Create and manage API tokens.
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.
Creating a Jira Cloud Token
For detailed steps and specific permissions for the Jira user, refer to our guide Connection.
Generate a Jira Data Center API token API token
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.
4. Establish a Connection with Jira:
Select the Jira app. Then enter your Jira instance URL (without "/" at the end), username, the Access token generated, the URL of the instance hosting the Getint Forge app in the bottom field, and click Add.
Select the Jira project(s) you want to synchronize and select Connect.
5. Choose and Connect the Second Jira Project:
Repeat the process on the other side. Since you are connecting Jira with Jira, repeat the steps.
6. Configure 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 issue types (Task, Bug, Epic, Story, Incident) and map them one-to-one.
7. Configure Field Mapping
Select the fields to synchronize, such as Title, Description, Assignees, and Custom fields. After all fields and types have been configured, give your integration a distinctive name and save the settings.
8. Assignees Mapping:
Map assignees according to your organization’s requirements.
9. Status Mapping
Map status fields to align between Jira and Jira. For example, To do in Jira, one Jira could be mapped to Open in the other Jira.
10. 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.
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.
Synchronization Directions
The platform supports three distinct logic flows for these items:
Bidirectional: Updates to comments or attachments in either Jira or Jira will reflect in the other platform.
Unidirectional to Jira: Data flows exclusively from Jira to Jira. Changes made in Jira will not sync back to Jira.
Unidirectional to Jira: Data flows exclusively from Jira to Jira. Changes made in Jira 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.
Comment Privacy
You can control the visibility of comments synced between Jira and Jira. The integration supports toggling between public and private comments freely, so you can configure public comments on one side to appear as private on the other, and vice versa. This gives your teams full control over what is visible to end users versus internal staff across both platforms.
Jira Group Restrictions
For Jira, you can limit comment synchronization based on Jira Groups. This ensures that only comments belonging to specific groups are shared across your projects, which is useful for organizations that need to keep certain discussions internal to a team or department.
For a full overview of filtering logic, AND/OR conditions, and date-based filtering, refer to the Comments Filtering documentation.
11. Filtering Options:
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 (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.
12. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between your JIRAs.
Verification Steps
Initial Creation:
Create a test ticket in the initial Jira.
Create a test issue in the secondary Jira.
Confirm that the items appear on the respective platforms according to your mapping rules.
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 Jira ticket updates accordingly.
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
By following these steps, you have established a functional integration between your Jira workspaces. This setup automates the synchronization of records, workflows, and communication, bridging the gap between support and development teams.
For further assistance, please get in touch with us at the Support Center or Schedule a Demo.
Last updated
Was this helpful?