Page tree

You are viewing documentation for Structure Server and Data Center version 5.6 and patch releases. For other versions, see Version Index or Structure Cloud.

Skip to end of metadata
Go to start of metadata

Dark Feature - Synchronizers are hidden by default

We recommend using Automation instead of Synchronizers. Automation is safer, provides additional functionality and flexibility, and uses fewer system resources.

To enable synchronizers, see Advanced Configuration and Dark Features.


The Sub-Tasks Synchronizer automatically places sub-tasks under their respective parent issues in the structure.

This synchronizer is available only when Sub-Tasks are enabled in your Jira instance and you have at least one Sub-task issue type defined.

Sub-Tasks Synchronizer Parameters

You can select which sub-task issue types the synchronizer works with. Issues of other issue types will not be affected.

This synchronizer only supports Import / Resync into Structure (more about resync).

Sub-Tasks Synchronizer Rules

  • When there is a sub-task (of one of the selected types) and its parent issue is in the structure, the sub-task is also added to the structure and placed under its parent task.
  • The parent issue must be in the structure already - the synchronizer does not add the parent AND sub-task, nor does it add a parent if the sub-tasks is already added.

    You can add parent issues to structure manually, or use a Saved Filter synchronization to add parent issues (and probably sub-tasks) automatically.

  • If a sub-task is already in the structure, and is located under a different parent (or at the top level), it will be moved under its subtask parent (with all sub-issues that it may have).
  • Changes in structure are not synced back to sub-tasks: if you place an issue under another issue, it will not become a sub-task.
    • If you move a sub-task away from its parent task, it will soon be moved back by the synchronizer.