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

5th of May 2020

Structure 6.0.1 provides performance and security related fixes

Download from Archive 
Structure on the Atlassian Marketplace


1. Patch Release

This is a small patch release based on Structure 6.0. It provides performance and security related fixes.

Upgrade is recommended for all customers using Structure 6.0.

2. Installation

If your Jira server does not have Structure yet, the installation is simple:

  1. Download and install the Structure add-on, either from Atlassian Marketplace or from our Download page. Pick the correct version based on your Jira version!
  2. When the Add-on Manager reports a successful installation, click Get Started to visit a page with important guidance for the Jira administrator. You may also want to check out the user's Get Started page, available under the "Structure" top-level menu.
  3. Monitor catalina.out or jira-application.log for log messages from Structure.

3. Upgrade

If you're upgrading from version 2.11.2 or earlier, please read Structure 3.0.0 Release Notes.

The upgrade procedure for versions 3.x to 6.0.x is simple:

  1. Consider backing up Jira data. Use Administration | System | Backup System. Starting from version 3.0.0, Structure data can be backed up together with Jira data. (If you have a large instance and have a proper backup strategy in place, you may skip this step.)
  2. Install the new version of the plugin.

  3. Monitor catalina.out or jira-application.log for warnings or errors.

4. Enterprise Deployment Notes

Structure 6.0.1 introduces attribute caching optimizations for structures with pinned items.

This is designed to reduce memory consumption for structures which are loaded on Issue View pages because they contain pinned issues. Since structures are not shown on the Issue View pages of issues added through Automation, this is particularly important for instances with huge structures built by synchronizers or containing large amounts of static content.

  • No labels