Page tree

You are viewing documentation for Structure Server and Data Center version 6.1 and patch releases. For other versions, see Version Index or Structure Cloud. | ALM Works Business Continuity During the COVID-19 Outbreak

Skip to end of metadata
Go to start of metadata

One of the most important features of Structure is its ability to visualize large amounts of issues in the hierarchical form based on the relationships which exist between the issues, the field values and other criteria. For example, you can automatically place stories under their epics, and sub-tasks under their parents, or group issues by Sprints, Fix Versions or assignees.

There are two mechanisms for building such structures: Automation and Synchronizers.

  • Automation is the preferred option, which we recommend using whenever possible.
  • While there may be some exceptions, Synchronizers are rarely a better option. Synchronizers were the original mechanism for building dynamic structures, but it was replaced by Automation in Structure 3.0 and is gradually being faded out.

To learn more about the differences between Automation and Synchronizers, and the considerations you should take when selecting which to use for your project, see:

  • No labels