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

24th of December 2019

Structure 5.6.2 provides Jira 8.4 compatibility fixes and more.

Download from Archive 
Structure on the Atlassian Marketplace

 

1. Patch Release

This is a patch release based on Structure 5.6.1. It provides:

  • Compatibility with Jira 8.4+.
  • Fixed: Epic Link colors now appear correctly in gadget.
  • Fixed: “Archived” label appeared next to search type when a search is opened.
  • Fixed: After collapsing and expanding structure levels, user could not select status for the Structure.Testy add-on.
  • Additional bug fixes.

Upgrade is recommended for all customers using Structure 5.6.x

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 5.6 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 5.6.2 does not introduce changes that could affect performance or would justify additional load and stress testing for Enterprise deployments.

  • No labels