Versions Compared

Old Version 18

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user spg bot

Saved on

Key

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

...

  1. Synchronization direction:
    • synchronization disabled,
    • synchronize only from TFS / Azure DevOps (formerly VSTS) to JIRAJira,
    • synchronize only from JIRA Jira 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.

Warning

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

Warning

Jira subtasks cannot have their own subtasks, so you cannot synchronize multi-level TFS / Azure DevOps (formerly VSTS) work item hierarchies to Jira subtasks.

Case study

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

...

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


  2. Jira Subtask has been created by user.
    Gliffy
    namebasic-2
    pagePin5


  3. After synchronization the JIRA 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
    nameBasic-3
    pagePin

...

  1. 6


  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
    nameBasic-1
    pagePin7


  2. A Task with parent/child relationship has been created by user in TFS / Azure DevOps (formerly VSTS).
    Gliffy
    namebasic-22
    pagePin5


  3. After synchronization a new Subtask is created in JIRAJira.
    Gliffy
    namebasic-33
    pagePin6

...

  1. JIRA Jira Subtask is correctly synchronized to child TFS / Azure DevOps (formerly VSTS) Task.
    Gliffy
    namebasic-33
    pagePin6


  2. JIRA Jira Subtask has been promoted by user to a regular JIRA Jira Task.
    Gliffy
    namepromote-1
    pagePin4


  3. After synchronization the parent/child link is removed in TFS.
    Gliffy
    namepromote-3
    pagePin4
  1. JIRA Jira Subtask is correctly synchronized to child TFS / Azure DevOps (formerly VSTS) Task.
    Gliffy
    namebasic-33
    pagePin6


  2. The parent/child link has been removed in TFS / Azure DevOps (formerly VSTS).
    Gliffy
    nameremove-1
    pagePin4


  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
    nameremove-1
    pagePin4
  1. We have two distinct JIRA Jira Tasks that are correctly synchronized to two TFS / Azure DevOps (formerly VSTS) Tasks.
    Gliffy
    namepromote-3
    pagePin4


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


  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
    namepromote-1

 

 

 

...

  1. pagePin4