Overview
Hierarchy works differently in Jira and Azure.
Jira has a three-level hierarchy (Subtask → Standard Work Item → Epic).
Azure has an unlimited level hierarchy available since it's done by Parent/Child link relation. Visual represenation of 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.
Azure → Jira: When Parent/Child link is added to from mapped work item to epic in Jira there is created EpicLink between those work items.
Jira → Azure: When work item is added to an epic there is Parent/Child relation link created in Azure.
<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.
Azure → Jira: When Parent/Child link is created in Azure from work item mapped to Jira subtask, there will be Jira subtask created
Jira → Azure: When there is subtask created in Jira, there will be Azure work item with type provided in mapping created and linked to it's parent by Parent/Child link.
<img of settings here>
Emulating multilevel Azure hierarchy in Jira
When using synchronizer there is an option to define a relation link in Jira that will correspond to Parent/Child link that go beyond Jira three-level hierarchy.
Relation link in Jira can be "on the top of" epic, "on the bottom of" subtask or between.
When nor Epic nor Subtasks are enabled, Items(TO CHANGE: if we change name) works as standard link synchronization.
<img of settings here>
Example configurations
Three level Azure configuration (Basic Azure DevOps process):
<img here>
Four level Azure configuration (Agile Azure DevOps process):
<img here>