...
- Synchronization direction:
- synchronization disabled,
- synchronize only from TFS / VSTS to JIRAJira,
- synchronize only from JIRA Jira to TFS / VSTS,
- synchronize in both direction.
- TFS / VSTS link type that maps to JIRA Jira subtasks (Default: Parent->Child).
- 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 / VSTS work item types.
| Warning |
|---|
Due to technical limitations JIRA Jira does not support changing issues to subtasks and subtasks to issues. |
| Warning |
|---|
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 Jira and TFS /VSTS workflows and default settings of synchronization profile.
New Subtask has been created in
...
Jira
- Let's assume that we have a JIRA Jira Task that is synchronized to a TFS / VSTS Work Item.
Gliffy name Basic-1 - JIRA Jira Subtask has been created by user.
Gliffy name basic-2 - After synchronization the JIRA the Jira Subtask is synchronized to new TFS / VSTS Task, and a parent/child link is established in TFS / VSTS.
Gliffy name Basic-3
...
- Let's assume that we have a TFS / VSTS Work Item that is synchronized to a JIRA a Jira Task.
Gliffy name Basic-1 - A Task with parent/child relationship has been created by user in TFS / VSTS.
Gliffy name basic-22 - After synchronization a new Subtask is created in JIRAJira.
Gliffy name basic-33
...
Jira Subtask has been promoted to a regular Task
- JIRA Jira Subtask is correctly synchronized to child TFS / VSTS Task.
Gliffy name basic-33 - JIRA Jira Subtask has been promoted by user to a regular JIRA Jira Task.
Gliffy name promote-1 - After synchronization the parent/child link is removed in TFS.
Gliffy name promote-3
The parent/child link has been removed in TFS / VSTS
- JIRA Jira Subtask is correctly synchronized to child TFS / VSTS Task.
Gliffy name basic-33 - The parent/child link has been removed in TFS / VSTS.
Gliffy name remove-1 - Due to technical limitations JIRA Jira Subtask corresponding to child TFS / VSTS Task is not changed to a regular Task after synchronization.
Gliffy name remove-1
A parent/child link has been created in TFS / VSTS
- We have two distinct JIRA Jira Tasks that are correctly synchronized to two TFS / VSTS Tasks.
Gliffy name promote-3 - New child/parent relationship has been added by user in TFS / VSTS.
Gliffy name promote-1 - Due to technical limitations JIRA Jira Task corresponding to child TFS / VSTS Task is not changed to Subtask after synchronization.
Gliffy name promote-1
...