> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/use-cases.md).
# Use Cases
## Introduction
Getint is a versatile platform for integrating, synchronizing, and migrating data across software tools and systems. Configurations range from a simple one-to-one, one-way transfer to a complex many-to-many, bi-directional sync, and the same platform covers both continuous synchronization and one-time migration.
It runs as a Jira Cloud app (built on Atlassian Forge), a Jira Data Center or Server app, or a self-hosted On-Premise deployment behind your firewall, and it connects Jira with 20+ tools, including Azure DevOps, ServiceNow, Salesforce, GitHub, GitLab, Zendesk, Monday.com, and Asana. The scenarios below show how teams put this to work.
### Integration Patterns
Most use cases are a combination of a few basic patterns. Understanding them helps you map your own scenario:
* **One-to-one**: A single project or instance connected to one other project or instance (for example, one Jira project to one Azure DevOps project).
* **One-to-many**: A single Jira project or instance connected to several tools or instances at once, each with its own field mapping and routing rules.
* **Many-to-many**: Multiple sources synchronized with multiple targets, often with Jira acting as the central hub.
* **One-way vs. bi-directional**: Data can flow in a single direction (source to target only) or in both directions, with each side updating the other automatically.
* **Continuous Sync vs. Migration**: Keep two systems aligned on an ongoing basis, or move data once as part of a transition.
Each connection keeps its own sync rules, filters, and automation triggers, so a single Jira work item can sync a different set of fields to each connected tool.
### Use Case Scenarios
#### Cross-team Visibility
1. **Jira to Asana, one-way integration**
* **Scenario**: A team tracks development in Jira while project managers plan in Asana. They need current visibility of Jira issues inside Asana without manual updates.
* **Solution**: Getint copies Jira issues to Asana tasks in one direction, so project managers see development progress in real time. Manual data entry is removed, which saves time and lowers the risk of errors.
2. **Multiple Tools Connected to Jira**
* **Scenario**: A company runs separate tools for different parts of the business, such as Salesforce for CRM, Trello for lightweight task tracking, Jira for development, and Zendesk for customer support.
* **Solution**: Getint connects these tools so that customer data, project updates, development issues, and support tickets move automatically between them. Every team works from current information, which supports faster communication and decisions.
#### IT Service Management and Support
3. **Jira and ServiceNow, Bi-directional Integration**
* **Scenario**: An IT team works in ServiceNow while a software development team works in Jira. Incidents, problems, changes, and service requests need to stay consistent across both.
* **Solution**: Getint sets up bi-directional sync between Jira (or Jira Service Management) and ServiceNow. ServiceNow incident events flow to Jira and updates flow back, giving both teams a shared, current view and removing duplicate ticket handling.
4. **One Jira to Multiple ServiceNow Instances**
* **Scenario**: An organization uses one Jira instance for issue tracking while several business units or customers each run their own ServiceNow instance.
* **Solution**: Getint configures bi-directional synchronization between the single Jira instance and each ServiceNow instance. Data flows correctly to the right unit, with separate filters per connection so each side only receives the items relevant to it.
5. **Zendesk to Jira, Support to Engineering**
* **Scenario**: Customer-reported bugs arrive in Zendesk, but the fixes are tracked by developers in Jira. Support and engineering lose time copying details back and forth.
* **Solution**: A Zendesk ticket creates a linked Jira issue, and comments and status updates sync in both directions. Support agents stay in Zendesk, developers stay in Jira, and neither team has to chase the other for updates.
#### Development and DevOps
6. **Jira and Azure DevOps**
* **Scenario**: Product planning happens in Jira while development is tracked in Azure DevOps, including hybrid setups where Jira Cloud needs to connect to an Azure DevOps Server instance.
* **Solution**: Getint syncs Jira issues with Azure DevOps work items, including comments, attachments, statuses, and hierarchy. Planning and delivery stay aligned across both systems without manual reconciliation.
7. **GitLab or GitHub to Jira**
* **Scenario**: Developers work in a code repository, and the team wants pull requests, commits, and branch activity reflected on the related Jira issues instead of being copied over by hand.
* **Solution**: Getint brings repository activity from GitLab or GitHub into the linked Jira issues automatically. It stays reliable at a scale where manual updates are no longer practical, and it keeps development context visible inside Jira.
#### Sales, CRM, and Product Feedback
8. **Jira and Salesforce**
* **Scenario**: Sales and support log customer requests in Salesforce, while product and engineering manage the backlog in Jira. Customer feedback needs to reach the people who build the product.
* **Solution**: Getint provides real-time, two-way sync between Salesforce records (cases, tasks) and Jira issues, with comments, attachments, statuses, and custom fields mapped between them. The Getint license is only required on the Jira side, which keeps setup simpler. Getint supports Salesforce Lightning and Classic, along with the major Jira deployments.
9. **HubSpot and Jira**
* **Scenario**: A go-to-market team manages deals and tickets in HubSpot, while engineering tracks the underlying work in Jira.
* **Solution**: Getint links HubSpot records with Jira issues so customer-facing teams and engineering stay aligned on status and progress without manual handoffs.
#### Jira-to-Jira Collaboration
10. **Jira to Jira Across Product Teams or Business Units**
* **Scenario**: A company builds several products, for example, phones, computers, and smartwatches, with each team working in its own Jira project or instance and its own workflow.
* **Solution**: Getint synchronizes data across these Jira environments and filters which projects and items are shared, so teams collaborate where their work overlaps while keeping appropriate access boundaries. This works across Jira Software, Jira Service Management, and Jira Data Center.
11. **Cross-company Jira to Jira**
* **Scenario**: Two organizations collaborate on shared work, but a partner cannot or does not want to install additional apps in their Jira.
* **Solution**: Getint syncs work items, fields, comments, attachments, and statuses between both Jira instances. With a Remote License, Getint is installed on only one side, so the partner does not need to add any apps.
#### One Hub, Many Tools
12. **Single Jira Hub Feeding Multiple Teams and Tools**
* **Scenario**: A company wants each team to keep using its preferred tool while management gets a single, company-wide view. As an illustration, a biking company runs Jira as its central hub, with Azure DevOps for developers, ServiceNow for customer service, Asana for marketing, and Salesforce for sales.
* **Solution**: Getint connects each tool to the central Jira hub, with tailored filters per connection (for example, syncing only tasks tagged for a given quarter or campaign). Each integration is given a clear name for easy management, and management gets a consolidated overview across every team and tool. For setups involving four or more instances, a Flexible License covers the connections.
#### Advanced and conditional synchronization
13. **Workflow and Field Mismatches Handled with Scripting**
* **Scenario**: Two connected systems use different workflows or field structures. For example, Jira requires a task to pass through an “in review” status before “done,” while ServiceNow moves directly from “in progress” to “done.” In another case, many fields on the source side need to be merged into fewer fields on the Jira side, with different dropdown values.
* **Solution**: On top of the no-code UI, Getint supports JavaScript-based scripting for advanced logic. Scripts can perform the correct intermediate Jira transition, transform and merge field values during sync or migration, and apply custom rules per event. The UI handles standard mapping, and scripting handles the exceptions, so simple cases stay simple and complex cases are still possible.
#### Hybrid and restricted environments
14. **Cloud and Data Center Hybrid, or Fully On-premise**
* **Scenario**: An organization runs a mix of Jira Cloud and on-premise Jira Data Center, or operates in an air-gapped or tightly restricted network where cloud connectivity is limited.
* **Solution**: Every deployment type is supported as both source and target, including a Jira Cloud instance syncing with an on-premise Jira Data Center instance. For restricted networks, Getint can be deployed On-Premise and run entirely behind your firewall. Data Center and Server connections use personal access token authentication.
#### Data Migration
15. **Moving Data Between Deployments or Tools**
* **Scenario**: A team is moving from Jira Server to Jira Cloud, or switching tools, for example, from Asana to Jira or from Monday.com to Zendesk, and needs to bring its data along while staying operational.
* **Solution**: Getint migrates issues, custom fields, comments, attachments, and related data as a one-time transfer, and can keep both systems in sync during the transition so teams keep working throughout the move.
### Benefits of Using Getint
* **Time Savings**: Automating data transfer removes manual copying and pasting, so teams can focus on higher-value work.
* **Accuracy and Reliability**: Automated synchronization reduces human error and keeps important data consistent across platforms.
* **Better Collaboration**: Connecting tools gives teams a shared, current view, which supports clearer communication and project management.
* **Data Integrity**: A single source of truth is maintained across systems, so every stakeholder works from the same up-to-date information.
* **Flexible Deployment Options**: Choose Jira Cloud, Jira Data Center or Server, or a fully self-hosted On-Premise setup behind your firewall.
* **Security and Compliance**: Getint is ISO 27001 and ISO 27018 certified, SOC 2 Type II audited, Cloud Fortified by Atlassian, a participant in a Bug Bounty program, and GDPR compliant.
* **Room to Grow**: Start with a basic one-to-one integration and expand to multiple instances, tools, and advanced scripted logic as your needs change.
### Choosing the Right Licensing for Your Scenario
Different use cases map to different licensing options:
* **Standard Dual Licensing**: The Getint license is installed on both Jira instances in a Jira-to-Jira integration, so each instance is licensed and able to communicate.
* **Remote License**: For a fixed fee, Getint is installed on only one Jira instance and syncs with another that does not have the app, which suits collaboration with a partner who prefers not to install anything.
* **Flexible License**: A custom license for managed service providers or organizations integrating four or more instances (for example, up to ten instances), with no restriction on which tools are involved.
For non-Jira integrations, the Getint license is generally required only on the Jira side, which keeps setup and procurement simpler.
### Example Configurations
The diagram below illustrates common topologies you can build with Getint:
The examples shown include:
* Jira integrated with another Jira instance.
* Jira integrated with Asana.
* Jira integrated with multiple ServiceNow instances.
* Jira integrated with Jira, ServiceNow, and Azure DevOps together.
* Jira integrated with several Asana instances and Trello.
* Jira integrated with Trello, Asana, GitLab, and Wrike.
Each configuration uses the same building blocks: a connection per tool, type, and field mapping (set up quickly with Quick Build or mapped manually), optional filters and scripting, and your choice of one-way or bi-directional flow.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.getint.io/use-cases.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.