4th of April, 2017
Structure 3.6 is another step towards integration with third-party add-ons. Now Structure supports grouping by Account field from Tempo Timesheets. Apart from that, the release contains a number of fixes and smaller improvements.Important for Structure 2.x users! If you currently use Structure 2.11.2 or an earlier version, it is very important that you read Structure 3.0 Release Notes before upgrading.
Download the latest Structure and Extensions
Structure 3 Demo Server
Structure 3 Quick Start Guide
When building your structures you can now easily track progress and see distribution of time spent, remaining estimates and other values by Accounts that you have set up in Tempo Timesheets. To do that, simply add a Group Generator for Tempo Account, select if you want to see closed and archived accounts and if you want to be able to move issues between accounts in structure. You can use this grouping both in Automation (when building a structure) and in Transformations.
Structure supports Tempo 8.2.4/Tempo Account 3.0.7.
The previous version introduced support for Portfolio Parent links (both Group and Extend). This version adds compatibility with the latest versions of Portfolio.
The following issues have been addressed in Structure 3.6:
The new version also contains other bug fixes and improvements.
Structure 3.6 and all extensions support JIRA versions from 7.1 to 7.3.x. All editions of JIRA (JIRA Core, JIRA Software, JIRA Service Desk) are supported. JIRA Data Center is supported.
This release is backwards-compatible with Structure 3.5, so all Structure extensions – Structure.Pages, Structure.Testy, as well as Colors plugin and other plugins that integrate with Structure 3.5 – should work with the new version.
If your JIRA server does not have Structure yet, the installation is simple:
catalina.out
or jira-application.log
for log messages from Structure.Upgrade procedure from versions 3.x is simple:
Install the new version of the plugin.
catalina.out
or jira-application.log
for warnings or errors.Structure 3.6 has a few changes in the core parts that could potentially affect performance and stability of the system. The changes are part of the ongoing improvement to optimize memory and database footprint by having a procedure of removing unused "rows" from Structure. This optimization itself is not yet turned on in Structure 3.6.
Rigorous testing has been carried out on the release candidate. The suggestions below provide further means to assure seamless deployment.
Please create Structure backup before upgrading. Turn off Backup History option unless you really need it.
You can try load testing and stress testing Structure 3.6 and JIRA on a staging environment before upgrading.
It makes sense to test the following parts:
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.