...
The following examples show how subtasks synchronization works in practice with default 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 Task that is synchronized to a TFS / VSTS Work Item.
Gliffy name Basic-1 - JIRA Subtask has been created by user.
Gliffy name basic-2 - After synchronization the JIRA Subtask is synchronized to new TFS / VSTS Task, and a parent/child link is established in TFS / VSTS.
Gliffy name Basic-3
New child Task has been created in TFS / VSTS
- Let's assume that we have a TFS / VSTS Work Item that is synchronized to 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 JIRA.
Gliffy name basic-33
JIRA Subtask has been promoted to a regular Task
- JIRA Subtask is correctly synchronized to child TFS / VSTS Task.
Gliffy name basic-33 - JIRA Subtask has been promoted by user to a regular 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 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 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 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 Task corresponding to child TFS / VSTS Task is not changed to Subtask after synchronization.
Gliffy name promote-1
...