Integration Overview
An integration connects two applications and defines how items are synced between them. Each integration has its own configuration, mappings, filters, and execution rules. This page explains how integrations are structured and how they work behind the scenes.
Integration Sections
Each integration contains several configuration areas:
Applications Icons
Displays the two applications connected by this integration.
It is also possible to change the connection and use a Query or JQL for advanced filtering by clicking the icons. See the documentation: Filtering Items for Integration in Getint and How to Use JQL Filters for Jira Integrations.
More
Here, you can access and control the integration interval between runs (Onpremise and Data Center deployments), the trigger behavior, ownership, and other execution rules. You can also disable the integration and export it.
Under this section, you will also find Advanced Configuration. It includes scripting options and advanced logic for cases that require customization. You can discover more about Advanced Scripting or contact us for help.
Items Filtering
Allows you to filter which items should be synced.
You can include or exclude items based on fields, conditions, or specific values. For more details on how to use the filters, check our documentation: Filtering Items for Integration in Getint.
Integration Name
If a name is not provided, Getint will give it a Generic name with the creation date when selecting “Create”; the name can be changed at any time.
Here you can also see the status, integration owner, the date of creation, and the access it was given.
Type Mapping
Defines how item types from one application translate into work item types in the other.
Within Type Mapping, you can:
Map work item types between both applications.
Copy configuration to reuse the same mapping settings.
Disable a mapping without removing it.
Access to edit the field mappings.
Delete a mapping.
Migration Configuration
Used when migrating existing or legacy items between applications. See more about migration options and configurations on our guides: Migration Guides.
Structure of an Integration
Integrations are built around Type Mappings.
A type mapping tells Getint how to translate a Work Item type from one system when it’s created or updated in the other.
Example
Jira might use (not limited to):
Task
Bug
Story
Azure might use (not limited to):
Task
User Story
Issue
If you want an Issue in Azure to create a Bug in Jira, you simply map Issue → Bug.
Work items that are not included in any mapping will not be synced.
Here, you can also use the Quick Build to facilitate the mapping of work items and fields, map dependencies, and manage the fields.
Mapping Multiple Types Into One
You can map several item types on one side into a single type on the other.
Example:
Jira Bug, Task, and Story → Azure Issue
When Azure needs to create the corresponding Issue, Getint uses the first matching work item type from the top of your mapping list.
How Integrations Run
Integrations run automatically based on the interval defined in Settings (For Cloud users, the minimum interval is 180 seconds).
Here’s how the execution works:
Getint checks the integration run interval in Settings.
When the scheduled time is reached, the integration starts.
For each connected application, Getint looks for all changes since the last run.
Only items that match your Type Mappings, Filtering Rules, and Sync Logic are processed.
Each execution is logged and can be viewed in Reporting → Runs.
This provides a clear record of what happened, when it occurred, and which items were synced.
Need Help?
If you have questions while setting up your integration, or if something doesn’t behave the way you expect, feel free to reach out. Our support team is happy to help you troubleshoot, review your configuration, or point you in the right direction. Contact us directly through our help page.
Last updated
Was this helpful?