Subtasks synchronization can be enabled in the "Field Mappings" 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 JIRA to TFSTFS / Azure DevOps (formerly VSTS) to Jira,
   • synchronize only from TFS to JIRAJira to TFS / Azure DevOps (formerly VSTS),
   • synchronize in both direction.
2. TFS / Azure DevOps (formerly VSTS) link type that maps to JIRA Jira subtasks (Default: Parent->Child).
3. Subtasks Mappings - JIRA  Jira allows to define many various issue types of subtasks (Please see JIRA Jira documentation for details). You can define here how they will be mapped to TFS / Azure DevOps (formerly VSTS) work item types.
   
   

Case study

The following examples show how subtasks synchronization works in practice with default JIRA Jira and TFS workflows /Azure DevOps (formerly VSTS)  workflows and default settings of synchronization profile.

New Subtask has been created in

...

Jira

1. Let's assume that we have a JIRA Jira Task that is synchronized to a TFS / Azure DevOps (formerly VSTS) Work Item.
   

   Gliffy
   name Basic-1

   JIRA

   pagePin 7

   
   
   
2. Jira Subtask has been created by user.
   

   Gliffy
   name basic-2

   JIRA

   pagePin 5

   
   
   
3. After synchronization the Jira Subtask is synchronized to new TFS / Azure DevOps (formerly VSTS) Task, and a parent/child link is established in TFS / Azure DevOps (formerly VSTS).
   

   Gliffy
   name Basic-3

...

1. pagePin 6

New child Task has been created in TFS / Azure DevOps (formerly VSTS)

1. Let's assume that we have a TFS / Azure DevOps (formerly VSTS) Work Item that is synchronized to a JIRA a Jira Task.
   

   Gliffy
   name Basic-1 pagePin 7

   
   
   
2. A task Task with parent/child /parent relationship has been created by user in TFS / Azure DevOps (formerly VSTS).
   

   Gliffy
   name basic-22

   The child TFS Task is synchronized -

   pagePin 5

   
   
   
3. After synchronization a new Subtask is created in JIRAJira.
   

   Gliffy
   name basic-33 pagePin 6

...

Jira Subtask has been promoted to a regular Task

1. JIRA Jira Subtask is correctly synchronized to child TFS / Azure DevOps (formerly VSTS) Task.
   

   Gliffy
   name basic-33 pagePin 6

   
   
   
2. JIRA Jira Subtask is has been promoted by user to a regular JIRA Jira Task.
   

   Gliffy
   name promote-1

   The

   pagePin 4

   
   
   
3. After synchronization the parent/child link is removed in TFS.
   

   Gliffy
   name promote-3 pagePin 4

The parent/child link has been removed in TFS

...

/ Azure DevOps (formerly VSTS)

1. Jira Subtask is correctly synchronized to child TFS / Azure DevOps (formerly VSTS) Task.
   

   Gliffy
   name basic-33 pagePin 6

   
   
   
2. The parent/child link has been removed in TFS / Azure DevOps (formerly VSTS).
   

   Gliffy
   name remove-1 pagePin 4

   
   
   
3. Due to technical limitations JIRA Jira Subtask corresponding to child TFS / Azure DevOps (formerly VSTS) Task is not changed to a regular Task after synchronization.
   

   Gliffy
   name remove-1 pagePin 4

A parent/child link has been created in TFS / Azure DevOps (formerly VSTS)

1. We have two distinct JIRA Jira Tasks that are correctly synchronized to two TFS / Azure DevOps (formerly VSTS) Tasks.
   

   Gliffy
   name promote-3 pagePin 4

   
   
   
2. New child/parent relationship has been added by user in TFS / Azure DevOps (formerly VSTS).
   

   Gliffy
   name promote-1 pagePin 4

   
   
   
3. Due to technical limitations JIRA Jira Task corresponding to child TFS / Azure DevOps (formerly VSTS) Task is not changed to Subtask after synchronization.
   

   Gliffy
   name promote-1

...

1. pagePin 4