Message-ID: <1597913213.15908.1711699236466.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_15907_585071468.1711699236466" ------=_Part_15907_585071468.1711699236466 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Structure 4.6.3 Release Notes

Structure 4.6.3 Release Notes

11th of May 2018

Structure 4.6.3 fixes a = problem in Performance Audit Log diagnostics system and has several perform= ance improvements.

Download from Archive 
Structure on the Atlassian Market= place

 

1. Patch Release

This is a patch release based on Structure 4.6.1. (There was no 4.6.2 re= lease.)

We have fixed a problem that caused collection of Performance Audit Log = to fail when Jira had a saved filter with an empty JQL, a JQL with only an = "order by" clause, or an invalid JQL. This problem could prevent collection= of valuable diagnostic data for ALM Works support team.

We also added five various performance improvements that are important f= or large instances (Server and Data Center), especially when there are freq= uent issue changes (for example, one issue per second).

Upgrade is recommended if you have encountered the problem with Performa= nce Audit Log or if you have a large Jira instance.

You need a Structure license with active maintenance (expiring not earli= er than May 11th, 2018) to upgrade.

2. Installation

If your Jira server does not have Structure yet, the installation is sim= ple:

  1. Download and install Structure add-on, either from Atlassian Marketplac= e or from the Download page.
  2. When the Add-on Manager reports about successful installation, click Ge= t Started to visit a page with important guidance for the Jira administrato= r. You may also want to check out the user's Get Started page, available un= der "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.

Upgrade procedure from versions 3.x and 4.x is simple:

  1. Consider backing up Jira data. Use Administration | System | Ba= ckup System. Starting from version 3.0.0 Structure data can be bac= ked up together with Jira data. (If you have a large instance and have prop= er 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

There is a number of small changes in Structure 4.6.3 that are not visib= le to the user (except for improved performance).

The following a is a list of affected components with suggestions of how= they could be tested on a staging server.

  1. Attribute loading subsystem: it is used when values are loaded into the= Structure grid. We removed additional checks for concurrent changes that h= appened during the loading of attributes. This will speed up the attribute = loading, and on a busy system it will drastically increase the responsivene= ss of the application. To test the subsystem, open different structures and= make changes to the issues. Check how totals and formulas are being recalc= ulated. Try to load-test the staging instance by having a constant flow of = issues changes while a structure with an inserter and a generator are being= used.
  2. Sub-task extender, Agile Rank sorter, Agile synchronizer, Sub-task sync= hronizer: the performance of these components was improved by changing the = way issues are checked for being sub-tasks. The performance improvement wil= l have bigger effect on systems with hundreds of issue types.
  3. Automation subsystem: eliminated some inefficiencies during generator e= xecution. To test, check the most frequently used automated structures. Try= changing values in Jira and see the generated structure update. If you are= using issue security, verify a limited user's access to issues. Check how = transformations and quick transformations work.

Additionally, we improved the user interface of Performance Audit Log.

------=_Part_15907_585071468.1711699236466--