Jira
Getint: Simplifying Jira Integration and Data Synchronization
Getint is expertly designed to integrate and synchronize an extensive range of tools. It accommodates a variety of connectivity scenarios, such as Jira - Jira, Jira - Azure DevOps, Jira - Asana, Jira - ServiceNow, and more. With its availability as both a Software-as-a-Service (SaaS) and On-Premise solution, Getint offers the versatility to meet the unique requirements of various businesses.
What does this article cover?
Getint enables seamless data synchronization within the same platform or different platforms/instances. It supports Jira and Jira Service Management of all types (Cloud, Server, Data Center), and across different projects. Allowing users to efficiently track and manage Jira tickets, tasks, bugs, and epics in diverse Jira environments as well as integrating Jira with other platforms.
Setting up Getint for Jira
Getint simplifies data integration and migration. With easy setup steps, you can connect your systems, such as Jira, map types (i.e. Task - Task), and fields (i.e. Priority - Priority). Whether you're looking to sync data or perform a one-time migration continuously, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to setup your Jira integration, please make sure to check the following:
Here's a simplified version of how to integrate Jira with other tools (you can find a detailed overview here):
Access the Getint App in Jira: Navigate to Jira, go to “Apps,” and select “the Getint app.” Select “Create Integration” then “Continuous Sync” or “Migration” based on your requirements.
Token Generation for Jira Cloud: Visit Atlassian Account Settings. Go to Security Navigate to the API Token section and generate a token. This token serves as the password for the Jira Cloud.
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 establish a new connection with your Jira instance. Name your connection, and add the URL of your Jira instance (without “ / “ at the end). Provide the login credentials.
Choose and connect the second app: Choose and connect another tool you'd like to integrate with your Jira—either another Jira instance, DevOps, ServiceNow, Salesforce, or any other tool that we support.
Map Types and Fields: Link Jira types (Task, Bug, Epic, Story) to synchronize with other tools. You can use the “Quick Build” feature, which allows you to map available fields automatically or you can set them manually.
Getint's support team is committed to ensuring a smooth and efficient integration experience customized to your unique needs. If you encounter any challenges during setup or require assistance with missing functionalities, our dedicated support team is readily available to provide guidance and assistance.
Supported fields in Jira
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
How Field Mappings Work:
One-Way Mapping:
When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
Two-Way Mapping:
Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
Tip:
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. Here’s an article explaining this in more detail: Here’s an article explaining this in more detail.
Limitations to be considered
At Getint we’re constantly updating our supported features, fields, and compatible apps. However, there are a few limitations you should be aware of:
When a new issue is created in Jira by Getint, it will always be one type of issue, whether that's a Task, an Epic, a Feature, or a Bug. You can set the default item type using a rule or manually change it in Jira after it's created.
Comments will be added as the user you choose to create the connection. Therefore, it is advised to create a dedicated Service Account to build your integration. The original author will appear in the comment footer, however, it will still be assigned to the account that established the connection.
History of changes can't be integrated.
Contacting our support team
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a call here.
Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our Case Studies, which are true accounts of how Getint continually enhances and improves the tool integration process.
Are you looking for a specific solution that we don’t currently support? Please get in touch with our support team, and we can assist you in developing a customized solution for your particular case.
Last updated