Jira - Azure DevOps: Epics and Subtasks Synchronization
Last updated
Was this helpful?
Last updated
Was this helpful?
Integrating Jira with Azure DevOps can significantly improve team collaboration and workflows. One of the key aspects of this integration is syncing Epics and Subtasks between the two platforms. This article will guide you through the process of setting up and maintaining subtask synchronization using a third-party tool called Getint.
Ensure that Epics and Tasks are mapped accordingly between Jira and Azure DevOps. Match the counterpart items on both sides of the integration.
When mapping Epics from Jira, don't forget to also map the Epic Name (if available). Otherwise, the epics will fail to create.
Open the Task - Task type mapping. Then, click on the Hierarchy tab, and check the box to enable the Epic relationship. Afterward, display the dropdown option and select the corresponding parent link for both sides.
For Subtasks, access the relevant type mapping. Next, activate the Synchronize Subtasks relationship. Finally, open the dropdown menu and choose the Parent Link option. Determine whether the subtasks should synchronize with their counterpart or be linked to a specific parent task by providing the task's ID.
After enabling this feature, any new Epics and Subtasks will be automatically synchronized with their parent/child task on Jira and Azure DevOps.
Click Apply to submit the changes and save your integration.
Respect hierarchy levels: Use Quickbuild to automatically align type mappings and create links. For manual integration, order issues correctly to prevent sync errors: Epics first, Stories/Tasks/Bugs second, and Subtasks last.
For existing projects: Move or bulk-move issues in order, starting with Epics, followed by Tasks and Subtasks. This ensures proper sync with existing parents on the other side.
Do not modify the Hierarchy options within Epics as this will break the integration. Only enable relationships for Stories/Tasks/Bugs and Subtasks.