Subtask support depends on the tool you are using. While some tools support infinite levels of subtasks (e.g. Wrike) others don't support subtasks at all (e.g. Github).
Unito syncs only one level of subtasks.
Sub-subtasks (level ≥ 2), when replicated into a one-level-only tool, will be ignored. Rest assured though, the full subtask hierarchy inside the original tool will remain unaffected.
To turn on the option to sync subtasks when creating or editing your sync, head over to the "More opitions" tab:
While Trello does not have subtasks, they do have checklists, which Unito will fully sync to other checklists or subtasks.
Unito syncs Asana subtasks, but only one level deep - we don't replicate the full infinite subtask structure.
Jira supports only one-level deep subtasks. They are synced with other tools supporting one-level deep subtasks (e.g. Asana) and tools that support infinite-level deep subtasks (e.g. Wrike).
Can't see where to add a subtask? Make sure you have this feature enabled first.
Unito syncs Wrike subtasks, but only one level deep. Just like Asana, we don't replicate the full infinite subtask structure here.
Github, Gitlab, Bitbucket, and Basecamp
None of these tools support subtasks on the issues that we sync. As a result, Subtasks will not be synced into any of these tools (we have nowhere to put them!), but they will also not be affected in the origin tool.
Wrike supports putting a subtask under multiple parent tasks. When replicated onto another tool supporting one-level deep subtasks, the subtask will be put under the highest ancestor task that is also part of the folder being synced. If the Wrike subtask doesn't have any parent/ancestor in the current project, the subtask will be replicated as a regular issue on the other tool.
Advanced Operations: Changing the Subtask's Parent,
Converting a Subtask to a Task & Vice Versa
Sometimes you need to move a subtask to another parent, demote a task to subtask level, or promote a subtask to a full-blown task. These advanced operations are possible in both Wrike and Jira.
Any such change on the Jira side will be carried over to the Wrike side. However, due to limitations of the Jira API, if these operations are applied from Wrike, the synchronization process will not apply the change automatically on Jira.