Overview
Azure and Jira have different approach to item hierarchy.
While Jira allows for three-level hierarchy (Subtask → Standard Work Item → Epic), Azure does not restrict the number of hierarchy levels, allowing for unlimited Parent-Child relations in a single hierarchy tree.
Visual representation of Azure hierarchy depends on chosen processes and is up to 4 levels.
Epics synchronization
In order to synchronize epics user have to check Epics synchronization checkbox in hierarchy mapping page and map corresponding epic items in both systems.
This can be done in Mapping → Hierarchy Mapping
...
Jira → Azure: When work item is linked to an epic there is Parent/Child relation link created in Azure.
Example:
<img of settings here>
Subtasks synchronization
In order to synchronize subtasks user have to check Subtasks synchronization checkbox in hierarchy mapping page and map corresponding work item type in Azure to subtask item in Jira.
...
Jira → Azure: When a subtask is created in Jira, a corresponding Azure work item will be created and it will be linked to its parent with a Parent/Child link. Example:
<img of settings here>
Emulating multilevel Azure hierarchy in Jira
Because Azure hierarchy can consist of more than three levels and Jira supports only three, in order to reflect more complexed hierarchies, a relation link will be created. User can select what type of relation will be applied. This can be done under Mappings → Hierarchy.
This relation can link to either Epic (making this epic a child issue), Subtask (making this subtask a parent issue) or any work item in between. Example:
When neither Epic nor Subtask synchronization is enabled, Items section serves standard link synchronization only.
<img of settings here>
Example configurations
Three level Azure configuration (Basic Azure DevOps process):
...