Skip to end of banner
Go to start of banner

Synchronizing JIRA subtasks to TFS / VSTS links

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Current »

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 TFS / VSTS to Jira,
    • synchronize only from Jira to TFS / VSTS,
    • synchronize in both direction.
  2. TFS / VSTS 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 TFS / VSTS 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" TFS / VSTS work item to a parent work item, or unlink a TFS / VSTS 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 TFS / VSTS work item hierarchies to Jira subtasks.

Case study

The following examples show how subtasks synchronization works in practice with default Jira and TFS /VSTS  workflows and default settings of synchronization profile.

  1. Let's assume that we have a Jira Task that is synchronized to a TFS / VSTS Work Item.


  2. Jira Subtask has been created by user.


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

 

  1. Let's assume that we have a TFS / VSTS Work Item that is synchronized to a Jira Task.


  2. A Task with parent/child relationship has been created by user in TFS / VSTS.


  3. After synchronization a new Subtask is created in Jira.
  1. Jira Subtask is correctly synchronized to child TFS / VSTS Task.


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


  3. After synchronization the parent/child link is removed in TFS.
  1. Jira Subtask is correctly synchronized to child TFS / VSTS Task.


  2. The parent/child link has been removed in TFS / VSTS.


  3. Due to technical limitations Jira Subtask corresponding to child TFS / VSTS Task is not changed to a regular Task after synchronization.
  1. We have two distinct Jira Tasks that are correctly synchronized to two TFS / VSTS Tasks.


  2. New child/parent relationship has been added by user in TFS / VSTS.


  3. Due to technical limitations Jira Task corresponding to child TFS / VSTS Task is not changed to Subtask after synchronization.

 

 

 

 

  • No labels