Getint: Where every ticket finds it's place.
Support portalCase studiesSchedule a demo
  • Welcome to the Getint Documentation Hub
  • Getting started with Getint
    • About Getint / Concepts
      • How Getint works (how it syncs the data)
      • Onboarding
      • What is a Connection?
      • What Are Runs
      • One-directional / Bi-directional integration
      • Migration vs Integration
      • How Integrations Are Executed By Getint
    • Starting the Free Trial and Accessing the Getint App
      • Selecting the Correct app per license
      • How do I extend the trial of getint.io?
      • Jira Access and User Management
    • Deployment options
      • Getint for Jira Data Center / Jira Server
        • Getint Jira Server / Jira Data Center App (native)
        • Getint for Jira Data Center / Jira Server - Architecture
      • Getint for Jira Cloud
      • Getint On-Premise
        • Architecture
        • Installation
          • How to Install Getint On-Premise in Windows Server
          • On-Premise/Standalone Guide
        • Updating On-Premise
        • Cluster High Availability
    • Prepare for the integration
      • Understanding the difference between platforms you integrate
      • One-to-One, One-to-Many, and Many-to-Many integration
      • Simplifying Workflow Sync with Getint: Jira
    • Connectors
      • Jira
      • Asana
      • Azure DevOps
      • Freshdesk
      • GitLab
      • HubSpot
      • Monday.com
      • Notion
      • Salesforce
      • ServiceNow
      • Zendesk
  • Guides
    • Quickstart
      • Integration
      • Connection
    • Integration Guides
      • How to Map Fields
      • How to create a custom field in all supported software
      • Git Repository integration
        • Git Connector - Azure DevOps
        • Git Connector - GitHub
        • Git Connector - GitLab
      • Azure DevOps Asana integration
      • Jira Airtable integration
      • Jira Asana integration
        • Jira - Asana: Subtasks synchronization
      • Jira Azure DevOps integration
        • How to Setup a Connection with Azure DevOps On-Premise
        • Jira - Azure DevOps: Epics and Subtasks Synchronization
        • Syncing Dependencies between Jira and Azure DevOps using Getint
      • Jira ClickUp integration
      • Jira Freshdesk integration
      • Jira Freshservice integration
      • Jira GitHub integration
      • Jira GitLab integration
        • Attachments Sync in GitLab Integration
      • Jira HubSpot integration
      • Jira Jira integration
        • Jira Jira licensing
        • Time Tracking in Getint – One-Way Synchronization
      • Jira Monday.com integration
        • Synchronizing Attachments in a Monday.com Integration
        • How to Insert Monday.com Items into Specific Groups Using Getint
      • Jira Notion integration
      • Jira Salesforce integration
        • Salesforce OAuth Authentication
      • Jira ServiceNow integration
        • Creating a ServiceNow User for Getint Integration
        • ServiceNow OAuth authentication
        • Creating a Custom Field in ServiceNow
        • How to Restrict "Incident" Data to Specific 3rd Party Companies
        • How to Restrict Access to Specific Tables for Integration
        • REST API requests list
      • Jira Trello integration
      • Jira Wrike integration
      • Jira Zendesk integration
        • How to Manually Provide Zendesk Organization ID and Name
    • Migration Guides
      • Migrating Data with Getint
      • Migration support, and onboarding
      • Jira to Jira migration
      • Asana to Jira migration
      • Azure DevOps to Jira migration
      • GitLab to Jira migration
      • Jira to Monday.com Migration
      • Jira Zendesk migration
  • Using Getint
    • Core Features of Getint
    • Workflows
      • Type Mapping
      • Integrations List
      • Configuring Your Data Sync: Bidirectional and Unidirectional Options
      • Syncing Attachments
      • Hierarchy
      • Assignees (users) mapping
      • Mapping Labels
      • Filtering Items for Integration in Getint
        • Troubleshooting Sync Issues: Unmet Filter Conditions
        • How to Filter Comments
        • Filtering by Assignment Group and Status
      • Shared Mappings in Getint – Centralized Mapping for Efficient Integrations
      • How to Use JQL Filters for Jira Integrations
      • Integration status
      • Storing counterpart link in the task comment
      • Storing Reference IDs/URLs Across Integrations
    • Connections
      • Troubleshooting Getint Integration Connectivity Issues
      • Permissions Issue: Status Code 500
      • Editing Connections for Existing Integrations
      • Changing the URL or Transitioning Between Instances
      • Debugging Connections in Getint: How to Troubleshoot and Resolve Issues
    • Quick Build
    • Reporting
    • Notifications
    • Request type issue on Jira Service Management how to select and work with it
    • Integrating one project with many: Streamlining synchronization across multiple projects.
      • One to Many Project - El Ride Use Case
    • Transition Fields
    • Resync and Hard Resync
    • Synchronizing Existing Items on Both Sides
    • Handling Syncs for Deleted Items
    • Advanced Scripting
    • Platform Release History
      • Getint Version 1.82
      • Getint Version 1.81
      • Getint Version 1.80
      • Getint Version 1.79
      • Getint Version 1.78
      • Getint Version 1.77
      • Getint Version 1.76
      • Getint Version 1.75
      • Getint Version 1.74
      • Getint Version 1.73
      • Getint Version 1.72
      • Getint Version 1.71
      • Getint Version 1.70
      • Getint Version 1.69
      • Getint Version 1.68
      • Getint Version 1.67
      • Getint Version 1.66
      • Getint Version 1.65
      • Getint Version 1.64
    • Settings
      • Data Storage
      • Sharing Access Permission
      • How to Override Getint Behavior Using Custom Properties
  • Support, legal & others
    • FAQ
      • Technical FAQ
      • Security FAQ
    • Troubleshooting Guide for Getint Users
      • Resolving Error 500 in Jira ServiceNow Integration
      • Locating Your Instance ID for Support
      • Connection Error: Certification Path Failed/PKIX Path Building Failed
      • Error: Field '<field-name>' cannot be set. It is not on the appropriate screen, or unknown
      • Connection timed out error
      • Troubleshooting: Integration Task Retrieval Error
      • Upgrade to newest version from version lower than 1.52
      • Debug Requests Feature
      • Troubleshooting: Resolving Hanging Integration Runs in Getint
      • Troubleshooting License Issues in Getint
    • Security and compliance
    • Support / SLA
    • Privacy & Security
      • Data Residency with Getint
    • Procurement & Legal
      • Enhanced Support for Vendor Onboarding and Security Assessments
      • EULA
      • Privacy policy
  • Billing & Services
    • Transparent and User-Friendly Pricing
    • Consulting and Custom Development
    • Understanding Getint Licensing and Pricing
      • How to pay for the apps
      • Migrations
      • Network License
      • Jira-Jira Licensing Model
      • Partners
      • Seamless Transition Offer: Migrate from Competitors to Getint with Exclusive Benefits
  • Use cases
  • Pricing Comparison: Getint vs. Alternatives
  • Battlecards (getint.io vs competitors)
  • Free migration from ConnectAll, Backbone, Exalate, Unito, Workato, TFS4JIRA and other tools
  • Anything missing? Getint is feedback driven
Powered by GitBook
On this page
  • Field Naming Variations:
  • Tool-Specific Fields and Custom Field Creation:
  • Inline Image Support Inconsistencies:
  • Out-of-the-Box vs. Custom Fields:
  • Mandatory Fields Variance:
  • Item Type Diversity:
  • Hierarchy and Structure Complexity:
  • API Documentation and Usability:
  • Read-Only Field Integration:
  • Custom Field Support:
  • Integration Limitations and Custom Solutions:
  • Workflow Mechanisms and Compatibility:
  • Integration of Collaboration Tools: Detailed Technical Perspective

Was this helpful?

  1. Getting started with Getint
  2. Prepare for the integration

Understanding the difference between platforms you integrate

Integrating different tools using Getint involves navigating various technical nuances. Understanding these subtleties ensures effective data synchronization and functionality across systems.

Field Naming Variations:

  • Different tools often use different terminologies for similar fields. It’s crucial to identify these variations and establish a mapping (e.g., Jira's 'Summary' to Azure DevOps' 'Description').

Tool-Specific Fields and Custom Field Creation:

  • Some fields are unique to specific tools (e.g., 'Assignment Group' in ServiceNow, 'Area Path' in Azure DevOps).

  • Technical Note: To integrate these unique fields, you may need to create corresponding custom fields in the other system to store this data. This ensures that all relevant information is captured and synced accurately.

Inline Image Support Inconsistencies:

  • Different tools have varying capabilities for embedding images within items. This should be considered when setting up integrations to ensure compatibility.

Out-of-the-Box vs. Custom Fields:

  • Tools like Jira offer numerous pre-defined fields, while others, like Monday.com, may start with fewer and require customizations for additional fields.

Mandatory Fields Variance:

  • The presence and enforcement of mandatory fields differ across systems, affecting how data is entered and synchronized.

Item Type Diversity:

  • The range of item types varies significantly among tools, influencing how data is categorized and managed during integration.

Hierarchy and Structure Complexity:

  • The level of hierarchical complexity in tools can vary, impacting how sub-items are managed and synchronized.

API Documentation and Usability:

  • The quality and detail of API documentation can greatly affect the ease of integration setup and customization.

Read-Only Field Integration:

  • Some fields in certain tools are read-only and can be integrated in only one direction.

  • Technical Note: To enable bi-directional integration for such fields, a corresponding writable custom field may need to be created in the other system. This allows for two-way data flow while respecting the read-only nature of the original field.

Custom Field Support:

  • The extent and flexibility of custom field support can vary, affecting how specific data points are handled during integration.

Integration Limitations and Custom Solutions:

  • Each tool has its unique limitations regarding integration. Identifying these early can help in determining the need for workarounds or custom development.

Workflow Mechanisms and Compatibility:

  • The complexity and nature of workflow configurations differ across tools, which should be considered for maintaining process integrity during integration.

In summary, technical preparation and a deep understanding of each tool’s capabilities and limitations are key to a successful integration process with Getint. Custom field creation, proper mapping, and accommodating for read-only fields are just some of the technical strategies that can be employed to ensure seamless integration across diverse systems.

Integration of Collaboration Tools: Detailed Technical Perspective

Integrating various collaboration tools using Getint requires a deep understanding of each platform's unique features and limitations. Here's an expert-level breakdown focusing on common collaboration tools and their differences:

Jira and Azure DevOps:

  • Jira's 'Epic Link' correlates to Azure DevOps' 'Parent Work Item'.

  • 'Sprint' in Jira aligns with 'Iteration Path' in Azure DevOps.

ServiceNow and Salesforce:

  • ServiceNow's 'Assignment Group' can be mapped to a custom field in Salesforce, as Salesforce doesn’t have a direct equivalent.

  • 'Incident State' in ServiceNow differs from 'Case Status' in Salesforce in terms of the lifecycle of a ticket.

Asana and ClickUp:

  • Asana's 'Sections' are similar to ClickUp's 'Lists' within projects.

  • 'Tags' in Asana can be equated to 'Labels' in ClickUp for categorization.

Monday.com and GitLab:

  • Monday.com’s 'Pulse' is conceptually similar to GitLab's 'Issue'.

  • Custom status columns in Monday.com need to be mapped to GitLab's 'Issue Status'.

GitHub and Wrike:

  • GitHub's 'Issues' can be mapped to 'Tasks' in Wrike.

  • 'Milestones' in GitHub have a different implementation compared to Wrike’s 'Folders/Projects'.

Hubspot and Trello:

  • Hubspot’s 'Deals' can be somewhat paralleled to Trello’s 'Cards' in a sales pipeline board.

  • 'Contact' in Hubspot versus 'Member' in Trello reflects the CRM versus project management focus.

Zendesk and Jira Service Management:

  • 'Ticket' in Zendesk corresponds to 'Issue' in Jira Service Management.

  • Zendesk's 'Views' for ticket organization are different from Jira Service Management's 'Queues'.

Read-Only and Custom Fields:

  • Tools like Jira and Azure DevOps allow extensive custom fields, which might need to be created in other systems like Monday.com or Trello for a complete sync.

  • For read-only fields in systems like Salesforce (e.g., 'Created Date'), corresponding writable fields may be necessary in the integrated tool to facilitate bi-directional data flow.

In each case, understanding the specific functionalities and limitations of these tools is crucial. This knowledge informs the creation of custom fields and the mapping process to ensure accurate data synchronization. It's also important to consider the hierarchical structures, workflow mechanisms, and API capabilities of each tool for a successful integration.

PreviousPrepare for the integrationNextOne-to-One, One-to-Many, and Many-to-Many integration

Last updated 1 year ago

Was this helpful?