29th of November, 2017
Now you can quickly change issue status simply by dragging it from one Status group folder into another. This version also contains several bug-fixes and some improvements for our performance diagnostics tool.
1. Version Highlights
Changing issue status using drag and drop.
- Support for Jira 7.6.
- Issue count is now displayed for the selected panel in double grid layout.
- Performance Audit Log includes more information.
2. Changes in Detail
2.1. Changing issue status in a structure
It is now possible to transition issues between statuses within a structure. Transitions that are allowed and do not have special workflow requirements (like required comments) can be done by simply moving issues between status groups.
2.2. Totals in double grid
In the double-grid layout, the number of items is now displayed for the panel that is currently in focus, as opposed to only left panel.
2.3. Changes to Performance Audit Log
Information about saved filters and filters used in generators or synchronizers is now available in Performance Audit Log.
It is now possible to save Performance Audit Log without scrolling to the bottom of the page: Save to File button is duplicated at the top.
2.4. Notable fixes and improvements
- Grouping by Customer Request Type is now possible with Service Desk 3.9.0.
- Fixed: Formula format would not work when Sum over sub-items checkbox was active.
- Fixed: Due In column would not show Overdue when past Due Date.
- Fixed: Work logged would not be displayed when filtered by users with usernames not in lower case.
3. Supported Versions
Structure 4.4 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.3. Structure.Testy extension, Colors plugin, integrations with our partner add-ons should work with the new version.
4. Installation and Upgrade
4.1. Installing Structure
If your Jira server does not have Structure yet, the installation is simple:
- Download and install Structure add-on, either from Atlassian Marketplace or from Download page. Pick the correct version based on your Jira version!
- When Add-on Manager reports the successful installation, click Get Started to visit a page with important guidance for the Jira administrator. You may want to also check out the user's Get Started page, available under "Structure" top-level menu.
- If you have Structure.Pages installed, make sure you've upgraded to version 1.3 or later, both on Jira and on Confluence side. If your Confluence version is not compatible with Structure Helper 1.3, you should stay with version 1.2 for .Pages and Helper add-on, but please, note that there are limitations to its compatibility with Structure 4.2 and higher, so Confluence upgrade to version 6.1 or better is recommended.
jira-application.logfor log messages from Structure.
4.2. Upgrading Structure
Upgrade procedure from versions 3.x–4.3 is simple:
- Consider backing up Jira data. Use Administration | System | Backup System. (If you have a large instance and have proper backup strategy in place, you may skip this step.)
- Back up Structure data. Use Administration | Structure | Backup Structure menu item. If you have a lot of structures and a large Jira, consider turning off "Backup History" option to avoid long backup process.
Install the new version of the plugin.
jira-application.logfor warnings or errors.
5. Enterprise Deployment Notes
Structure 4.4 does not have a lot of core changes compared to Structure 4.3.
5.1. Index Monitoring Improvements
In Structure 4.2 we introduced an experimental "dark feature" for Jira Data Center to work around a race between Structure's issue change notifications and Jira's own inter-node messages which cause changed issues to be re-indexed on all nodes. You can refer to Structure 4.2 release notes, section 5.1 for more information and detailed instructions.
Structure 4.4 improves this experimental event distribution subsystem to better handle full and single-project re-indexing operations. The changes are quite significant, so if you rely on this feature, it makes sense to test the new version on a staging environment before upgrading. If you have any questions, please contact email@example.com.
5.2. New Table for Generic Items
Generic items are simple items managed by Structure. They are much like Structure's folders, but they can also contain an icon and a description. Generic items are meant to be used by other ALM Works products and third-party apps that integrate with Structure. Only the server-side APIs and components are released with Structure 4.4, so it is not possible for users to create generic items at this point.
With the introduction of generic items we have added
AO_8BAD1B_GENERIC_ITEM table to the database schema. This table stores primary data (not stored anywhere else in Jira).
The data from this table is exported along other structure data when you do Structure Backup in a human and machine readable form. The table is also exported along with all Structure data during Jira backup.
We don't expect considerable database load on this table.
5.3. Testing on Staging Environment
There are no particular special areas of interest for load testing and stress testing Structure 4.4. We advise running the same testing procedures as you've done for previous upgrades.