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

Contents        

Subtasks synchronization can be enabled on Subtask Mapping screen (during new profile creation via wizard) or on Field Mappings on profile edit screen. The following settings are available:

  1. Synchronization direction:
    • synchronization disabled,
    • synchronize only from Azure DevOps to Jira,
    • synchronize only from Jira to Azure DevOps,
    • synchronize in both direction.
  2. Azure DevOps link type that maps to Jira subtasks (Default: Parent->Child).
  3. Subtasks Mappings - Jira allows to define many various issue types of subtasks (Please see Jira documentation for details). You can define here how they will be mapped to Azure DevOps work item types.

Due to technical limitations, Jira does not support changing issues to subtasks and subtasks to issues.
This means that if you link a "standalone" Azure DevOps work item to a parent work item, or unlink a Azure DevOps task from its parent work item, a corresponding Jira issue will not be changed to/from subtask.

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.
    Basic-1

  2. Jira Subtask has been created by user.
    basic-2

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


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.
    Basic-1

  2. A Task with parent/child relationship has been created by user in Azure DevOps.
    basic-22

  3. After synchronization a new Subtask is created in Jira.
    basic-33

Jira Subtask has been promoted to a regular Task

  1. Jira Subtask is correctly synchronized to child Azure DevOps Task.
    basic-33

  2. Jira Subtask has been promoted by user to a regular Jira Task.
    promote-1

  3. After synchronization the parent/child link is removed in Azure DevOps.
    promote-3

The parent/child link has been removed in Azure DevOps

  1. Jira Subtask is correctly synchronized to child Azure DevOps Task.
    basic-33

  2. The parent/child link has been removed in Azure DevOps.
    remove-1

  3. Due to technical limitations Jira Subtask corresponding to child Azure DevOps Task is not changed to a regular Task after synchronization.
    remove-1

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.
    promote-3

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

    promote-1

  3. Due to technical limitations Jira Task corresponding to child Azure DevOps Task is not changed to Subtask after synchronization.
    promote-1





  • No labels

This page has no comments.