You are viewing documentation for Structure Server and Data Center version 5.5 and patch releases. For other versions, see Version Index or [Structure Cloud].
28th of December, 2017
This version introduces duplicate items highlighting, which makes it much easier to find, review and delete duplicate issues in a structure. This version also includes several performance improvements and bug fixes.
Download the latest Structure and Extensions
Structure Demo Server
Duplicate items highlighting
Several performance improvements and fixes
Issues can appear in structure more than once both when added manually or automatically. You can now quickly find, highlight and switch between such issues in a structure. This makes working with duplicates much simpler. For example, if necessary, you can delete manually added duplicates or adjust automation settings to make sure automation only adds one instance of an issue.
Documentation: Identifying Duplicate Items
Structure 4.5 and all extensions support Jira versions from 7.2 to 7.6. All editions of Jira (Jira Core, Jira Software, Jira Service Desk) are supported. Jira Data Center is supported.
With respect to other add-ons and custom integrations, this release is backwards-compatible with Structure 3.4–4.4. Structure.Testy extension, Colors plugin and integrations with third-party add-ons should work.
If your Jira server does not have Structure yet, the installation is simple:
catalina.out
or jira-application.log
for log messages from Structure.If you're upgrading from version 2.11.2 or earlier, please read Structure 3.0.0 Release Notes.
Upgrade procedure from versions 3.x–4.4 is simple:
Install the new version of the plugin.
catalina.out
or jira-application.log
for warnings or errors.Structure 4.5 has a number of changes that are particularly important for large installations and Jira Data Center instances.
Big and deep structures built with multiple extenders have been a source of performance problems for some of our customers. Structure 4.5 contains numerous optimizations aimed at reducing both the generation time and memory consumption for such structures.
The changes to the extender implementations and the automation engine are quite substantial, so if you rely on large structures (10,000 issues or more) built with extenders, we advise you to perform load and stress testing on a staging environment before upgrading.
A fix in the Sprint grouper required it to load more data from Lucene. We do not expect this to be a problem, but if you rely on the Sprint grouper, it might make sense to test it before upgrading.
We have also optimized the attribute sub-system to speed up aggregate calculations on large, deep structures.
Given the changes described above, you can test the following scenarios:
Watch the log files for errors and warnings while running these experiments.
The usual load and stress testing can also be applied.
Should you have any questions on Enterprise Deployment, let us know at support@almworks.com.