Import Feature
Synchronizing Existing Items on Both Sides
Once an integration has been set up via Getint, newly created items on both sides will begin to synchronize. However, any items that existed before the integration was established (such as historical tickets synchronized manually or through another tool) will not sync. These pre-existing items may have been paired outside of Getint, but the initial integration won’t recognize such pairings. Possible cases include migrating from Exalate to Getint, TFS4JIRA to Getint, Backbone to Getint, or ConnectAll to Getint.
In this guide, we’ll explain how to link existing items between the tools to keep information aligned. This helps prevent duplicate tickets from being created and eliminates the need to manually delete existing content.
While we use specific connectors in our examples, this process applies to all Jira-related integrations.
How to Synchronize Existing Items in a Jira Integration
Please navigate to the integration and Disable it.
To avoid duplicate tickets, make sure your integration is disabled before making any changes. If it’s still active, the tool might see your updates as new items and end up creating duplicates.
We recommend disabling the integration at least 10 minutes before initiating this process to ensure all runs are fully terminated and prevent unintended duplication.
Go to Reporting → Synced items. Then click on Import.
In the Import screen:
Select the relevant integration.
Select the side of the integration that represents the app you want to import the issues from.
Select Automatically capture data of imported items if data capturing needs to be performed during the first run of the integration. The condition is that Jira must be the left-side app of the integration. NOTE: PLEASE do not mark this option if the Jira app is not on the left side of the integration.
Paste the relevant item IDs to be mapped from both sides. Sometimes, this list can be generated from one of the apps that the user is syncing. If you have stored a counterpart ID in a custom field, you can create a report with ID and COUNTERPART ID fields, which can be exported to XLS or CSV and then copied here.
The correct way to map item IDs would be as follows:
Task ID then a comma (,), and the counterpart ID.
Finally, click Apply to submit the changes.
Please note that Getint will not be aware of the pairing if Automatically capture data is not selected in the above steps.
Pairing Related Items with Bulk Changes in Jira
To pair related items, please follow the steps described below:
Log in to your Jira instance and navigate to the Search screen.
Fetch all the imported items in Jira (in this case, DEMO-1, DEMO-2, DEMO-3) and perform a bulk update by clicking on the 3 dots button on the right-hand side of the screen. You can add a label (for example, getint_import_sync) to perform an update on these items.
In the next screen, select all the relevant issues and click Next.
Choose Edit Issues in the next screen and click Next.
Go to Labels, check the box, and enter getint_import_sync, then click Next.
In the next screen, click Confirm. This will now bulk update all the related items.
Enable the integration (disabled above).
Once the integration is enabled and execution begins, only the data about imported items will sync during the first run. Subsequent integration runs will synchronize any applied changes according to the integration configuration.
IMPORTANT NOTE:
The import process restricts pairing to 200 records per run for cloud customers and 1000 for customers with DC apps or On-Premise. Ensure that pairing adheres to these limits, which are valid only for users with a full license.
The import process is limited to pairing 5 records if you are on a trial version.
Tutorial Video
How to Copy the Correct Work Item ID Based on Your App
Asana
Asana doesn’t show the issue ID up front, so you can either copy it from the task’s web address or add a custom field to retrieve each task ID. The easiest way to find it is through the task’s URL as shown in the below picture.
ServiceNow
ServiceNow also does not display the issue ID (referred to as the sys_id) in the user interface by default. However, the identifier can be retrieved through the task’s URL or by accessing the record details directly.
These are just two examples of how get IDs from other tools. If you're experiencing issues with the import process, it's a good idea to check with your technical team to confirm that you're pulling the correct work item ID from your app.
If you have any questions or need assistance, please do not hesitate to contact us at our Help Center or Schedule a Demo.
Last updated
Was this helpful?