Child pages
  • Synchronizing JIRA subtasks to Azure DevOps links - Cloud Native App

Versions Compared

Key

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

...

Warning

Jira subtasks cannot have their own subtasks, so you cannot synchronize multi-level Azure DevOps work item hierarchies to Jira subtasks.

Case study

The following examples show how subtasks synchronization works in practice with default Jira and Azure DevOps workflows and default settings of synchronization profile.

New Subtask has been created in Jira

  1. Let's assume that we have a Jira Task that is synchronized to an Azure DevOps Work Item.
    Gliffy Diagram
    displayNameBasic-1
    nameBasic-1
    pagePin1
    version2


  2. Jira Subtask has been created by user.
    Gliffy Diagram
    displayNamebasic-2
    namebasic-2
    pagePin2


  3. After synchronization the Jira Subtask is synchronized to new Azure DevOps Task, and a parent/child link is established in Azure DevOps.
    Gliffy Diagram
    displayNameBasic-3
    nameBasic-3
    pagePin2


New child Task has been created in Azure DevOps

  1. Let's assume that we have an Azure DevOps Work Item that is synchronized to a Jira Task.
    Gliffy Diagram
    displayNameBasic-1
    nameBasic-1
    pagePin2


  2. A Task with parent/child relationship has been created by user in Azure DevOps.
    Gliffy Diagram
    displayNamebasic-22
    namebasic-22
    pagePin2


  3. After synchronization a new Subtask is created in Jira.
    Gliffy Diagram
    displayNamebasic-33
    namebasic-33
    pagePin1
    version2

Jira Subtask has been promoted to a regular Task

  1. Jira Subtask is correctly synchronized to child Azure DevOps Task.
    Gliffy Diagram
    displayNamebasic-33
    namebasic-33
    pagePin1
    version2


  2. Jira Subtask has been promoted by user to a regular Jira Task.
    Gliffy Diagram
    displayNamepromote-1
    namepromote-1
    pagePin1
    version2


  3. After synchronization the parent/child link is removed in Azure DevOps.
    Gliffy Diagram
    displayNamepromote-3
    namepromote-3
    pagePin1
    version3

The parent/child link has been removed in Azure DevOps

  1. Jira Subtask is correctly synchronized to child Azure DevOps Task.
    Gliffy Diagram
    displayNamebasic-33
    namebasic-33
    pagePin2


  2. The parent/child link has been removed in Azure DevOps.
    Gliffy Diagram
    displayNameremove-1
    nameremove-1
    pagePin1
    version2


  3. Due to technical limitations Jira Subtask corresponding to child Azure DevOps Task is not changed to a regular Task after synchronization.
    Gliffy Diagram
    displayNameremove-1
    nameremove-1
    pagePin2

A parent/child link has been created in Azure DevOps

  1. We have two distinct Jira Tasks that are correctly synchronized to two Azure DevOps Tasks.
    Gliffy Diagram
    displayNamepromote-3
    namepromote-3
    pagePin3


  2. New child/parent relationship has been added by user in Azure DevOps.

    Gliffy Diagram
    displayNamepromote-1
    namepromote-1
    pagePin1
    version2


  3. Due to technical limitations Jira Task corresponding to child Azure DevOps Task is not changed to Subtask after synchronization.
    Gliffy Diagram
    displayNamepromote-1
    namepromote-1
    pagePin2

...