Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Azure and Jira have different approaches to item hierarchy.
While Jira allows for a three-level hierarchy (Subtask → Standard Work Item Issue Type → 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 the chosen process and is up to 4 levels.

...

Azure → Jira: When Parent/Child link is added to mapped work item for a mapped epic in Jira, there is EpicLink created between those work itemsissues.

Jira → Azure: When work item issue is linked to an epic there is Parent/Child relation link created in Azure.

...

In order to synchronize subtasks user has to check Subtasks synchronization checkbox in Configuration > Mappings > Hierarchy and map corresponding work item type in Azure to subtask item issue 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.

...

This relation can link to either Epic (making this epic a child issue), Subtask (making this subtask a parent issue) or any work item issue in between.

When neither Epic nor Subtask synchronization is enabled, Multi-level-hierarchy synchronization section serves standard link synchronization only (with forced Parent/Child link on Azure side).

...