Skip to end of banner
Go to start of banner

Synchronizing JIRA subtasks to TFS 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 16 Next »

Subtasks synchronization can be enabled in the "Field Mappings" screen. The following settings are available:

  1. Synchronization direction:
    • synchronization disabled,
    • synchronize only from TFS to JIRA,
    • synchronize only from JIRA to TFS,
    • synchronize in both direction.
  2. TFS 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 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 work item to a parent work item, or unlink a TFS task from its parent work item, a corresponding JIRA issue will not be changed to/from subtask.

Case study

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

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


  2. JIRA Subtask has been created by user.


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

 

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


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


  3. After synchronization a new Subtask is created in JIRA.
  1. JIRA Subtask is correctly synchronized to child TFS 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 Task.


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


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


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


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

 

 

 

 

  • No labels