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
  • How does it work
  • How to set up a Hierarchy
  • Considerations to take
  • Common issues when establishing a hierarchy
  • Conclusion

Was this helpful?

  1. Using Getint
  2. Workflows

Hierarchy

PreviousSyncing AttachmentsNextAssignees (users) mapping

Last updated 7 months ago

Was this helpful?

Hierarchy is crucial in organizing work, managing projects, and tracking progress. Within Getint, we provide the possibility to integrate your current workflow with other tools or across other Jira instances/projects. Therefore, setting the hierarchy levels is necessary to incorporate all issues efficiently.

How does it work

This feature is available for all type mappings when building an integration. However, it is important to note that not all apps support hierarchy in the same way as Jira, Asana, Monday, or Azure DevOps to name a few.

At its core, it revolves around different types of issues such as:

  • Epics: Represent high-level initiatives or large work items.

  • Stories/Tasks: Individual units of work that contribute to an epic.

  • Subtasks: Manageable tasks required to complete a story.

For example, this would be the standard hierarchy levels in a Jira to Jira integration. For other apps, please ensure you use type mappings that match the items on the other side (i.e. Epic - Epic, Task - Item, Subtask - Subitem).

At present, Getint allows to sync Hierarchy in a standard manner. While it works perfectly for simple scenarios, we’re currently working on improving the feature for more advanced use cases where the hierarchy tree consists of several hierarchy levels and uses links for defining relationships.

How to set up a Hierarchy

The feature is easily accessible within your type mappings, but it is required to select the correct options for an error-free synchronization.

Enabling the feature

  1. Go to your integration and open the corresponding type mapping. For stories/tasks that you would like to sync the Epic link, you’ll need to go to Hierarchy > enable Synchronize Epic relationship > display the dropdown and select the Parent Link (NextGen projects).

  1. For subtasks, open the corresponding type mapping > enable the Synchronize Subtasks relationship > display the dropdown and select the Parent Link.

Do not modify the Hierarchy options for Epics as this will break the integration. Only enable relationships for Stories/Tasks/Bugs and Subtasks.

  1. Save the changes and test your integration.

Considerations to take

Please make sure the following criteria are met when setting up your hierarchy. Otherwise, issues won’t sync properly.

  • Respect the hierarchy levels. The Quickbuild feature enables you to align your type mappings appropriately and automatically establishes links for available hierarchy relationships. However, if you’re building your integration manually, it is necessary to order the issues properly. Otherwise, sync will fail as Getint will try to create/update a task first without an existing parent. This would be the correct order: Epics first, Stories/Tasks/Bugs second, and Subtasks last.

  • Do not modify the Hierarchy options for Epics as this will break the integration. Only enable relationships for Stories/Tasks/Bugs and Subtasks.

  • When working with existing projects that have an established hierarchy, it’s advisable to move or bulk-move all the issues in order. For example, move all the Epics first to the other side, and then handle the Tasks and Subtasks afterward. This approach ensures that when updating any tickets or creating subtasks, they will sync accordingly since there’s already an existing parent on the other side.

Common issues when establishing a hierarchy

When establishing a hierarchy, it is crucial to follow all the recommended steps outlined in this article. Failing to do so may result in errors similar to those listed below.

Error

Invalid response status code received (expected: 201 but got 400). Response: {errorMessages":[]

errors:{"parentId":"Given parent issue does not belong to appropriate hierarchy."}}"

This error occurs when issues are not mapped in the correct sequence required to establish the hierarchy. For example, if the parent issue is not yet synced in the integration or if the items are mapped incorrectly. Additionally, if the hierarchy levels exceed what is currently supported, the workflow will not match the one that was mapped.

Error

Invalid response status code received (expected: 201 but got 400). Response: {errorMessages":[]

errors:{"parent":"Could not find issue by id or key."}}"

This error happens when Getint can't find or create the matching item on the other side. First, transfer all the issues and then set up the ParentLink. If the items are out of order, like Subtasks - Subitems, and then Tasks - Items, Getint will struggle to find the parent because it’s attempting to sync the Subtask ahead of everything else.

Error

Invalid response status code received (expected: 201 but got 400). Response: {errorMessages":[]

errors:{"issuetype":"Issue type is a sub-task but parent issue key or id not specified."}}”

This issue will occur when the hierarchy is not configured for subtask types.

Conclusion

Thanks to the Hierarchy feature, Getint allows users to sync issues with their respective parents and children without losing track of their progress. This opens a wide range of possibilities to group any stories, tasks, and subtasks to efficiently manage your workflows.

At Getint, we're dedicated to providing exceptional support throughout your integration journey. Our team is committed to delivering the best customer experience. For any questions about this integration or assistance with the setup process, don't hesitate to open a ticket at our or . We're here to help!

Support Center
Schedule a Demo
Incorrect order for type mappings
Having issues to build your integration? Schedule a free consultation with our Integration Experts now!
Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!