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