Structure Changelog

What's new in Structure 9.3.0

Apr 15, 2024
  • Planning Tasks:
  • Structure Planning Tasks are now the easiest way to plan your next project in Jira, without having to commit your early ideas to Jira issues:
  • Draft your entire project plan: add work, remove work, organize the work, and get everyone aligned before a single Jira issue gets created.
  • Once you're ready, easily convert your entire plan - or just some of your Planning Tasks - into Jira issues.
  • Planning Tasks also work with Generators, Formulas, and Structure.Gantt 4.2+ (releasing soon).
  • Additional Improvements:
  • Fixed: Structure.feature.altInitialValuesInDialog would not use data from selected issue
  • Fixed: Confluence gadget configuration could not be saved with a long filter name
  • Fixed: Dark feature to disallow changes in generator by default did not work as expected
  • Fixed: Line break in rich text editor did not work
  • Fixed: Automation rules (set via Automation from Jira) did not work when an update was triggered from Structure
  • Improved: Show username instead of the key in Key column

New in Structure 9.2.0 (Dec 22, 2023)

  • Assets data can be edited in columns, used in formulas, and more

New in Structure 9.1.0 (Nov 5, 2023)

  • Planned Time data available in columns, formulas, and more

New in Structure 9.0.1 (Aug 25, 2023)

  • Added: SEN number is now visible to logged in non-admin users on the Info pop-up
  • Fixed: Time tracking panel is duplicated when logging time in a structure for the first time
  • Fixed: Share with option becomes unresponsive if there are too many groups/projects in the create structure wizard
  • Fixed: Create item panel: width of name and description fields are not changed when resizing the details panel

New in Structure 9.0.0 (Aug 4, 2023)

  • Multiple Notes columns:
  • It's now possible to include multiple Notes columns within a structure, so you can take notes on as many topics as you need.
  • Additional memo fields:
  • Manage your high-level planning without affecting Jira: Memos can now include field data for Assignee, Due Date, and Time Tracking fields.
  • Additional Improvements:
  • Time in Status improvements: Time in Current Status option is now available
  • Tempo Worklogged Column: added the possibility to clear all accounts
  • Fixed: Activity Stream gadget performance
  • Fixed: Formula values with dates had inconsistent formatting in Excel Export
  • Fixed: Status groups were not localized in Excel Export
  • Fixed: Opened structure wasn't added to the recent list
  • Fixed: Issue Type Name was not localized
  • Fixed: Multi-Level Cascading Select app values could be added but not saved via inline editing

New in Structure 8.3.1 (May 24, 2023)

  • Fixed: Linked issues section sometimes collapses on the issue details panel after expanding
  • Fixed: Only the first 100 sprints are available in the Filter by Field dropdown
  • Fixed: Synchronizer is not migrated if user has a different key on the target Jira
  • Fixed: Jira 9.0 compatibility, XSRF Token missing on bulk edit

New in Structure 8.3.0 (Apr 26, 2023)

  • Tempo Work Logged column and formulas integration
  • Formula debugging tool
  • Effector conflict resolution

New in Structure 8.2.2 (Jan 26, 2023)

  • Fixed: Completed issues were shown in the Backlog group
  • Fixed: Impossible to download the S-JQL troubleshooting file on Jira 9.5
  • Fixed: Adding formula columns from Confluence gadget

New in Structure 8.2.1 (Jan 10, 2023)

  • Added: compatibility with other Structure apps for Jira Server/Data Center
  • Fixed: support multiple contexts in Filter by Field
  • Fixed: Jira hotkeys on the Manage Saved Columns page
  • Fixed: it was not possible to enter a date in the work logged column in Jira 9.5
  • Fixed: always use timezone of column creator in Saved Columns
  • Fixed: My Columns cannot be shared with a perspective link
  • Minor security fixes

New in Structure 8.2.0 (Dec 29, 2022)

  • New filter: Filter by field
  • Save and share formulas
  • Manage Structure page improvements: Last opening date and new UI for configuration (note: last opening date will be empty for old structures)

New in Structure 7.4.0 (Dec 22, 2021)

  • Access historical field values in formulas
  • Fixed: Can't use work logged attribute in formulas
  • Fixed: Aggregations are calculated incorrectly when called from an attribute group generator
  • Small UI improvements: style and color changes to the history panel, time tracking, and automation banner
  • Performance improvements

New in Structure 7.3.0 (Oct 24, 2021)

  • Fixed: a stability issue with the Structure gadget in Confluence, when making a request to Jira Data Center. More info
  • Fixed: Query match column did not handle 'Sum over sub-items' properly
  • Fixed: "attachments" variable wasn't automatically mapped in formula columns
  • Fixed: broken UI when hovering over fields with wiki markup
  • Fixed: Formula column with "Sum over sub-items" option selected could not be used as a variable
  • Fixed: exporting structures with complex formulas took significantly longer than expected
  • Fixed: icons were not displaying in the Confluence gadget

New in Structure 7.2.0 (Sep 1, 2021)

  • Allows you to group Quick Transformations, to apply multiple transformations at once.

New in Structure 7.1.0 (Jul 25, 2021)

  • Formulas now support comments from issues and worklog's (including Tempo Timesheets)
  • Notes column and Quick transformation data can now be included when copying a structure
  • Security patch

New in Structure 7.0.0 (Jul 25, 2021)

  • Structure 7.0 introduces Expr 2 - a completely new level of sophistication and possibilities within formulas.

New in Structure 6.6.0 (Jul 25, 2021)

  • Attribute filter
  • Grouper performance improvement
  • Security patch

New in Structure 6.5.0 (Feb 3, 2021)

  • Perspective sharing via email
  • Advanced Roadmaps (Portfolio) Team Effector
  • Additional improvements and fixes

New in Structure 6.4.0 (Dec 7, 2020)

  • Fix version and sprint details can now be shown in the Summary column and used in formulas
  • Option to show names, avatars or both in user columns
  • Additional improvements and fixes

New in Structure 6.3.2 (Nov 21, 2020)

  • Migration assistance to migrate structures from Server/Data Center to Jira Cloud
  • Fix to an issue that prevented Structure from reading the values of some custom fields

New in Structure 6.3.0 (Oct 11, 2020)

  • Structure 6.3 adds:
  • Status Rollup Effector
  • Default view for structures
  • Group by Project Category
  • Improved Information Center
  • Ability to edit numeric custom fields through Structure Gadget
  • Additional improvements

New in Structure 6.2.0 (Aug 11, 2020)

  • Effectors can write values to duration and multi-value fields
  • Full-screen formula editor
  • Last Comment column

New in Structure 3.5.0 (Feb 9, 2017)

  • New features::
  • Grouping by issue links
  • Specifying JQL or S-JQL as a filter in Structure dashboard gadget
  • Bidirectional issue link extender
  • Default level limit for extenders
  • This version also contains a critical security patch.

New in Structure 3.3.2 (Oct 19, 2016)

  • Addressed a problem with issue key link not working on the Issue Navigator page in Internet Explorer 11.

New in Structure 3.3.0 (Sep 16, 2016)

  • New features:
  • Migration of Structure data between JIRA instances (also allowing partial restore from backup)
  • S-JQL support for searching folders and other items
  • Special filter that removes duplicates added by a combination of inserters and extenders
  • Maintenance task that removes old structure change history (please check the defaults!)
  • Swapping panels in two-panel mode
  • JIRA 7.2 compatibility
  • Significant fixes and improvements related to performance and troubleshooting

New in Structure 3.1.1 (Jun 2, 2016)

  • Highlights:
  • Fixed: infinite generator creation in case of complicated structure.
  • Fixed: a deadlock caused by JQL generators using the structure() function.
  • Fixed: big syncronizer audit log retrieval.
  • Implemented: synchronizer audit log cleanup.

New in Structure 3.1.0 (May 7, 2016)

  • Added support for sorting by Script Runner's numeric custom fields.
  • Improved Structure database lock-out during restore from backup.
  • Fixed: Cannot upload changes after new issue creation fails.
  • Fixed: Field column does not use proper number formatting for totals.
  • Fixed: Excessive warnings from synchronization engine during restore from backup.
  • Fixed: Changing direction in sorting by resolution doesn't work.
  • Fixed: Error 500: "failed to upload structure changes" appears on creating issue under unavailable item

New in Structure 3.0.1 (Apr 12, 2016)

  • Multi-parent (same issue can be at multiple locations in any structure)
  • Folders (special non-JIRA folders for containing issues in structures)
  • Issue sorting and grouping
  • Structures within structures
  • Automation (automatic structure generation, an alternative to synchronizers)
  • Revamped user interface
  • JIRA Data Center compatible

New in Structure 2.10.3 (May 1, 2015)

  • Adds compatibility with JIRA Agile 6.7.

New in Structure 2.10.1 (Mar 27, 2015)

  • Adds compatibility with JIRA 6.4 and contains several bug fixes and improvements.

New in Structure 2.10 (Feb 24, 2015)

  • Compatibility with JIRA 6.4 - A number of changes introduced by JIRA 6.4 are incompatible with Structure 2.9.1 or earlier. This version fixes the incompatibilities.
  • Alternative Rank Synchronization:
  • JIRA Agile synchronizer now offers two ways to synchronize Rank back to JIRA Agile – Independent Ranking and Consecutive Ranking.
  • Independent Ranking means that the rank will be separately compared and updated for the issues that have the same "parent" issue. For example, if you have a structure with Epics at the top and Stories under Epics, rearranging Epics would only update the rank of Epics – their stories can be in different order. Likewise, if stories under one Epic are rearranged, their relative position on the Agile board is changed, but they can intermingle with stories from another Epic.
  • Consecutive Ranking means that the rank of all issues in a structure will be compared and updated, according to the issue's position in the structure. This means that if you drag an Epic before another Epic, all its Stories present in the structure also receive a higher rank than the stories in the other Epic.
  • Consecutive Ranking is the way Rank synchronization worked in Structure 2.9.1 and earlier versions. When upgrading, all existing synchronizers will have this option selected and retain the way they work. You can switch to Independent Ranking by editing existing synchronizers.
  • Documentation: JIRA Agile (GreenHopper) Synchronizer, Modifying Synchronizer
  • Additional option for Filter synchronizer:
  • Filter synchronizer also has got a new option when "Remove" mode is on – Double-check sub-issues. It concerns the way Filter synchronizer removes issues from structure – if a sub-issue passes the filter, but its parent doesn't, the parent issue is not removed – because that would mean removing the sub-issue too.
  • When Double-check sub-issues is on, and a parent issue is updated and no longer satisfies the filter, its sub-issues are also checked, even if they haven't been updated. (Normally they wouldn't be checked without an explicit event signaling their change.)
  • This option allows removal of parts of the structure based on a filter with calculated values, or on a filter with S-JQL queries.
  • Documentation: Automatic Branches Removal, Filter Synchronizer
  • Automatic Opening of Issue Details Can Be Turned Off:
  • With the introduction of Issue Details feature in version 2.9, Structure no longer would open separate issue page when an issue is clicked on the Structure Board. Instead, it would automatically turn on Issue Details panel, because it shows the same data but also shows you the hierarchy and saves you time to navigate to another page and back.
  • However, on smaller screens it can be inconvenient and we received feedback that some users would prefer to open the issue page, as it used to be in Structure 2.8 and back.
  • Normally, we'd like to avoid adding extra options when we can help it, but in this case about half of our users loved the new behavior, and half of them were annoyed by it.
  • So in Structure 2.10, it becomes a configurable option.
  • Recognition of Issues Being Not Editable According to Workflow:
  • Structure used to consider only the user's permissions when determining whether an issue can be edited. However, JIRA can be configured to disallow editing of issues in a specific workflow state. In fact, the classic JIRA workflow makes issues in Closed state not editable. Starting with version 2.10, Structure also considers the workflow.
  • This especially has impact on structures that have the Require Edit Issue Permission on Parent Issue flag set (see Structure Permissions for details). With this flag on, the users cannot rearrange the direct sub-issues of an uneditable issue – now, including closed issues under classic JIRA workflow.
  • If this change negatively affects you, please contact ALM Works Support. It is possible to revert this change without downgrading.
  • Other Improvements and Fixes:
  • There are important bug fixes and improvements in Structure 2.10, including:
  • Fixed: Filter sync doesn't remove stories with sub-tasks when Sprint field changes
  • Fixed: When many children are created in structure very quickly, Links Synchronizer may fail to create links
  • Fixed: Concurrent execution of a Filter synchronizer with inline issue creation may lead to move of the created issue regardless of the synchronizer's settings
  • Fixed: Filter synchronizer may ignore an issue if it was created inline on Structure Board, or if it was edited and then moved in structure
  • Fixed: Structure module is hidden on Issue Navigator in IE11 after changing search query

New in Structure 2.9.0 (Sep 9, 2014)

  • Version Highlights:
  • Viewing full issue details without leaving Structure Board
  • A column that shows work logged over a period
  • Visual notification after issues are removed from structure
  • Archiving old structures
  • JIRA administrators can change the owner of a structure
  • Copying a structure including installed synchronizers
  • Changes in Detail:
  • Issue Details on the Structure Board - Structure Board can now display full details of the selected issue in a right-hand panel, much like JIRA's issue navigator does. Just click the link to the issue in the Summary or Key column, or click the button in the top right corner to open issue details panel.
  • This feature lets you view full details of an issue and make any changes you'd usually make on the issue page, without leaving Structure Board and still observing the structure of all issues.
  • Keyboard Shortcuts: O (toggle details, switch keyboard focus to the details panel), Shift+O (toggle details without switching focus)
  • Work Logged Column - The new "Work Logged" column displays the total work logged over a specified period of time (unlike "Time Spent" field, which shows the all-time total work logged).
  • The column supports aggregation, so you can see the total work logged over a specific period for all sub-issues.
  • Issue Removal Notification - When issues are removed from the structure (either by pressing Delete key, or by clicking the Remove button in the Structure toolbar), a notification is shown briefly at the top of the page, with an Undo link. This should help with noticing and reverting the change if you hit Delete accidentally.
  • Archiving Old Structures - When you have a structure that is no longer updated and rarely looked at, but you still need to keep it for possible future reference, you can archive such structure. As a result, the structure is no longer suggested in the menus, it is made read-only and all synchronizers on the structure are deactivated.
  • Changing Structure Owner - JIRA administrators can now change the owner of a structure by using Configure link on the Manage Structure page.
  • The owner of a structure always has full Control access to the structure, so this feature helps when full access must be transferred from one person to another, such as when somebody leaves a project or the company.
  • Copying Structure with Synchronizers - When you make a copy of a structure (for example, when copying/cloning a template structure), you can select "Copy Synchronizers" option. As a result, the original structure's synchronizers are copied and installed on the new structure.
  • The copied synchronizers are initially disabled, so you need to manually Resync & Enable them.
  • Other Notable Improvements:
  • Structure gadget can be maximized on a JIRA Dashboard
  • Allow specifying custom title of the Structure gadget
  • Export to Excel toolbar button is now enabled on Mac OS X
  • Compact view of the Issue Key column, showing project icon and issue number

New in Structure 2.8.3 (Jul 26, 2014)

  • Fixes a problem with Agile boards in JIRA 6.3 and JIRA Agile 6.4.

New in Structure 2.8.2 (Jul 22, 2014)

  • Fixes compatibility problems with JIRA 6.3.

New in Structure 2.8.1 (Jul 17, 2014)

  • Fixes rank synchronization with JIRA Agile 6.4.

New in Structure 2.8.0 (Jul 12, 2014)

  • Adds support for JIRA 6.3 and introduces a Structure-based workflow validator, among other improvements and fixes.

New in Structure 2.7.0 (Feb 27, 2014)

  • Adds support for JIRA 6.2, integrates with the standard "Create Issue" dialog, and allows you to reconfigure installed synchronizers. We have also released Structure 2.6.1 patch for JIRA 5.2.

New in Structure 2.6.0 (Jan 25, 2014)

  • Sharing Perspectives - Did you ever want to show someone a part of a large structure, with all the columns and other presentation aspects configured exactly as you see them? Now you can share a Structure perspective. A perspective is a short link encompassing everything you see on the Structure Board – the structure, its visible part, all the columns, expanded, collapsed and selected issues, search terms, and more. You can create a perspective with a single click and send the link to other people or save it as a bookmark to return to it later.
  • Protection from Synchronizer Conflicts - It is possible to accidentally configure a pair of synchronizers that would revert one another's changes endlessly, leading to degraded performance and a lot of noise in the Activity Streams. Protection against such conflicts has been around since version 2.0, but with this release we make it more prominent; by default, Structure will disable the conflicting synchronizers and send e-mail notifications to the users who installed them.
  • Permissions for Project Roles - JIRA administrators can now grant access to Structure and the permission to create new structures to particular project roles – in addition to user groups. This can greatly simplify Structure permission configuration in certain scenarios. Please see Restricting User Access to Structure and Changing Permission to Create New Structures for more information.
  • Synchronization with Agile Boards - It is now possible to synchronize with a specific Agile Board – JIRA Agile synchronizer will use its query and ranking. We have also fixed a few bugs in Agile and Links synchronizers.
  • Progress Column Improvements - The configurable Progress column was introduced in Structure 2.5. In this release we've made several improvements to the progress aggregation algorithm to address the cases, noticed by our customers, where it yielded unpredictable or confusing results. We have also fixed a bug in the Icons column.

New in Structure 2.5.3 (Nov 25, 2013)

  • Fixes a few issues with synchronization and improves performance with very large structures.

New in Structure 2.5.2 (Nov 8, 2013)

  • It fixes one critical and one minor issue with JIRA Agile synchronization:
  • HJ-1548 JIRA Agile synchronizer pulling issues onto structure board incorrectly using epic link
  • HJ-1550 Editing Epic Link from the issue page doesn't trigger JIRA Agile synchronizer

New in Structure 2.5.1 (Nov 8, 2013)

  • Work Logging Fix - The following critical issue has been fixed:
  • HJ-1542 Work log may be placed under a wrong issue when entered with a button on a time tracking section of the issue page — this only affects JIRA 6 or newer.
  • Keyboard Shortcut Fixes - The following keyboard-related bugs have been fixed:
  • HJ-1505 Comment shortcut doesn't work
  • HJ-1507 View Full Size Image shortcut doesn't work
  • HJ-1523 Several keyboard shortcuts don't work in the Gadget
  • Synchronization Fixes and Improvements:
  • Links and Agile synchronizers now react to changes made via Edit Issue and workflow dialogs.
  • Other Agile synchronizer improvements include:
  • HJ-1295 In Agile synchronizer, don't link sub-tasks to epics if "Force Sub-tasks" is enabled
  • HJ-1072 Removed Epic may be restored when sub-issue is moved in structure within the same parent
  • HJ-1478 Epic Sync: Child issue isn't moved on the structure after removing epic
  • Other Improvements:
  • Our public JIRA contains the full list of issues resolved in version 2.5.1. One of them is notable: HJ-1525 Bulk change should process the issues in structure order — this is important if you use Xporter for JIRA.

New in Structure 2.5 (Sep 27, 2013)

  • Javascript API Release:
  • In this release we're adding JavaScript API to customize client-side functionality of Structure. As of Structure 2.5, it allows to create custom column types for the Structure widget. Please refer to Structure JavaScript API Reference for more information.
  • Minor Java API Release:
  • Structure API has been expanded — we've added support for custom columns for the Structure widget. This part of the API should supply the necessary data to the JavaScript API.
  • Compatible Changes in the Java API:
  • New package com.almworks.jira.structure.api.column - This package allows to define components that support custom columns. You can extend data fields that are provided to the Structure widget (data subpackage), and how the values are exported to Excel and printable format (export, excel, and printable subpackages.)
  • New package com.almworks.jira.structure.api.aggregate - This package allows to implement a custom column that aggregates values over structure through the means of implementing the Aggregate interface. There's a caching layer, so values will be recalculated only for the changed issues and all dependent issues.
  • Notably, progress aggregates such as the Progress Column are now implemented through this package (see progress subpackage.)
  • Deprecated classes:
  • ProgressCalculator and ProgressInfo classes are now deprecated; their counterparts from the new aggregate package – AggregateCalculator and progress.ProgressAggregateFactory – should be used instead. The latter supports the new, highly customizable Progress Column.
  • Other changes:
  • We've added methods for the new kinds of columns to ViewSpecification.
  • Due to the ability to rename projects in JIRA 6, we've added project ID-based methods to StructureConfiguration.
  • We've added new functions to extract data from JIRA issue to JiraFunc. They make for easy implementation of the new kinds of columns for a specific JIRA issue field.
  • New Plugin Module Types:
  • To extend Structure with new columns, you need to declare the extending components in your atlassian-plugin.xml using the new module types – structure-widget-extension, structure-issue-data-provider and structure-export-renderer-provider.

New in Structure 2.4.3 (Sep 3, 2013)

  • Adds workarounds for grayed out Sprint panel and occasional Chrome browser crashes.

New in Structure 2.4.2 (Aug 8, 2013)

  • Patch Release:
  • This is a patch release based on version 2.4.1. It fixes a problem that caused Time Tracking section on the issue page to disappear, even though the issue contained time tracking information.
  • The bug affected both JIRA 5 and JIRA 6 versions of the product.
  • Upgrade is recommended for all customers who have version 2.4.1 installed.
  • Supported JIRA Versions:
  • Structure 2.4.2 supports JIRA versions 5.0.1 – 6.0.x. There are two separate downloads: one for JIRA 5, another for JIRA 6.

New in Structure 2.4.1 (Aug 3, 2013)

  • Patch Release:
  • This is a patch release based on version 2.4. It fixes a rare but critical bug that could significantly slow down JIRA. Additionally, Structure section is now available on the detail view in the new Issue Navigator in JIRA 6. There are many other bug fixes and smaller improvements, most of which target user experience with Structure on the Issue Page.
  • Upgrade is recommended for all customers who have a license with active maintenance and a compatible JIRA.
  • Fixed:
  • some S-JQL queries run too slow and can cause OutOfMemoryError on the server
  • In Structure 2.4, we have introduced S-JQL, a way to find issues that satisfy structure-based conditions. Since then, we have discovered and fixed a major performance problem. The implementation of some relations (prevSibling, nextSibling, and sibling) was inefficient, so that running a structure() JQL query with these relations on a large structure (thousands of issues) could result in major performance degradation, in come cases causing OutOfMemoryErrors. The fix added in this version significantly improves the speed and reduces memory usage of these relations. We have improved other relations as well, so that almost all S-JQL queries now run faster.
  • Additionally, this version contains a fix for another problem that could cause memory shortage over time.
  • Fixed: issues with keys starting on "I" display Structure widget even if the project is disabled for Structure and other problems on the issue page
  • This bug was introduced in Structure 2.4: in JIRA 6, if there is a project with key that starts with "I" or "i", Structure section is displayed on pages of issues in this project. We have fixed this along with many other problems with user experience on the issue page.
  • Structure section is now available in the Issue Navigator:
  • Starting with JIRA 6.0, JIRA's Issue Navigator features the Detail View, so that users can work with issues in the context of the current filter. In this release, we add Structure section to the detail view.

New in Structure 2.4 (Jun 15, 2013)

  • Structured JQL:
  • In this version, we're happy to introduce a long-awaited feature — Structured JQL (S-JQL) language for finding issues in structures that satisfy some structure-based conditions.
  • Notable Fixes:
  • Fixed: HJ-1184 Status rollup synchronizer does not correctly respond to Delete Issue action
  • Fixed: HJ-1202 Send to Top / Send to Bottom don't work in Firefox
  • Fixed: HJ-1338 Multiple problems with IE8-IE9 and JIRA 6

New in Structure 2.3 (Jun 15, 2013)

  • JIRA 6 Support:
  • JIRA 6 is a major new upgrade from Atlassian, with overhaul of the user interface and many other improvements. Structure plugin has been modified to fit nicely into the new JIRA package.
  • Most of the updates for JIRA 6 were adapting Structure user interface to the new look, but we also migrated Structure to the new JIRA platform to support such features as the ability to change login name.
  • Fixes:
  • Fixed: HJ-1169 Make Structure panel show for issue of type "Test", added by Zephyr
  • Fixed: HJ-1232 Use the same link to Log Work action as on the standard Time Tracking section on the issue page (even if it is replaced by Tempo)
  • Fixed: HJ-1242 Status Rollup synchronizer fails to find a global transition
  • Fixed: HJ-1265 Link synchronizer may erroneously move an issue to the top
  • Fixed: HJ-1308 Printable page loses view configuration when view is locally modified

New in Structure 2.2.1 (Apr 13, 2013)

  • Contains an important bug fix and minor improvements.
  • Fixed: Possible Loss of Structure Due To Broken JIRA Index
  • Administrator's User Interface Improvement for Current Customers
  • Fixed: HJ-1233 Progress may be calculated incorrectly for an issue that has resolved sub-issue, which has non-resolved sub-sub-issue
  • Fixed: HJ-1206 Progress for parent issues is not updated after editing time in a child issue
  • Fixed: HJ-1198 Quote escaping in JQL is lost when going from Issue Navigator to Structure Board
  • Fixed: HJ-1205 Issue type drop-down does not contain default type
  • Fixed: HJ-1223 Structure gets package-refreshed for no reason when installed or when JIRA is started

New in Structure 2.2 (Mar 29, 2013)

  • Available for purchase on the Atlassian Marketplace.

New in Structure 2.1.1 (Mar 19, 2013)

  • Contains a critical fix for JIRA 5.2.8 and later versions.

New in Structure 2.1.0 (Feb 16, 2013)

  • Support for GreenHopper 6.1:
  • In version 6.1, GreenHopper team had introduced a new approach to epics, backed by a different set of custom fields, notably Epic Link and Epic Name. The old Epic/Theme field was deprecated and is used now only on classic boards. Structure 2.0 and earlier versions are not fully compatible with this change.
  • With Structure 2.1, you can continue using GreenHopper and Structure together:
  • GreenHopper synchronizer can now work with the new epics, synchronizing structure with epic-story assignment on the Scrum Board. When installing the synchronizer, select Scrum Board Epics as the "Epic Field". The synchronizer can still work with older Epic/Theme field as well.
  • When a new epic is created in the Structure Widget, and the Epic Name is not set by the user (it's a required field for epics), Structure automatically uses the value you have entered as the issue's Summary.
  • Structure section on the issue details panel in GreenHopper now enters "Pinned" mode by default, showing you only the parent issues and sub-issues of the selected issue. You can pin and unpin Structure widget as usual.
  • If you are upgrading Structure and already have GreenHopper synchronizer installed, it will continue working with the old Epic/Theme field. To switch to the new Scrum Board Epics integration, you need to use Manage Structures page to delete or disable the old synchronizer and create a new one.
  • Documentation: GreenHopper Synchronizer, Structure on GreenHopper Boards
  • Undo:
  • Structure 2.1 adds limited Undo functionality, which lets you revert a single recent change you've made to a structure. Not all operations can be undone, but those most frequently used – like removing issues from structure or drag-and-drop – can be reverted.
  • Automatic Daily Backup and Maintenance:
  • As Structure data is stored in its own database, it needs to be backed up separately from the main JIRA backup. That also means that the default automatic backup run by JIRA does not cover Structure data.
  • Starting from this version, Structure can automatically run daily maintenance procedure at the time specified by JIRA administrator. The maintenance procedure creates a backup of Structure data and performs several optimizations on the Structure database.
  • Structure Can Be Selected as "My JIRA Home":
  • You can now select Structure Board as your default page in JIRA (on JIRA 5.1 or later).
  • Click the profile menu in the top right corner and select Structure under My JIRA Home directory. After that, if you open JIRA in browser using its general address, Structure Board will be shown automatically, with the latest structure you've been working with.
  • Other Notable Improvements and Bugs Fixed:
  • HJ-1057 Exclude archived versions from version fields when creating new issues (with copying categories) and cloning issues
  • Fixed: HJ-1069 Repetitive call to the same workflow action through operations dialog fails
  • Fixed: HJ-888 minus-minus shortcut does not work in Firefox 15
  • Fixed: HJ-1059 Migration failure in case exported XML contains deleted issue ids
  • Fixed: HJ-1060 Export to Excel / Printable page do not work if the selected view is "Issue Navigator"
  • Fixed: HJ-1093 Structure grid displays unsupported JIRA columns when "Columns" mode is turned on
  • Fixed: HJ-1100 Rank to Top / Rank to Bottom actions don't close when called from "." operations menu
  • Fixed: HJ-1120 Issue type drop-down does not contain default type
  • Fixed: HJ-1140 Structure causes error when displaying GH tab for issue in not Structure-enabled project

New in Structure 1.7.0 (Jul 12, 2012)

  • Support for JIRA 5.1 (with support for the latest GreenHopper versions up to 5.10.x)
  • More flexible Filter synchronizer, with JQL Query and Allow Move options
  • Page reload not required on workflow transitions and most other JIRA actions, resulting in much smoother user experience

New in Structure 1.5.0 (Feb 18, 2012)

  • Support for the upcoming JIRA 5.
  • Support for GreenHopper 5.8.6 and the upcoming GreenHopper 5.9.

New in Structure 1.4.0 (Jan 9, 2012)

  • Editing Issues On-the-Grid: you can now change values of most issue fields right in the Structure widget.
  • Structure History: all changes to structures are now recorded and can be inspected with the Structure widget's history panel.
  • Activity Stream: you can now display changes to structures along with other changes in the Activity Stream dashboard gadget.
  • Export to Excel: the structure and issue fields can now be exported onto a neatly organized XLS file.

New in Structure 1.3.0 (Oct 24, 2011)

  • Structure API that allows other plugins and remote applications to work with Structure.
  • Big performance improvements for structures with many issues.
  • Compatibility with the latest JIRA 4.4.3 and GreenHopper 5.8 releases.

New in Structure 1.2.0 (Aug 31, 2011)

  • Structure Gadget allows to add several structure widgets to JIRA dashboard and view structure in Confluence.
  • Status Rollup Synchronizer changes status of a parent issue according to the statuses of its sub-issues. For example, you can make parent issue Resolved if all sub-issues are Resolved.
  • structure() JQL function selects issues from structure and lets you build complex JQL queries that involve structures.

New in Structure 1.1.1 (Aug 8, 2011)

  • A bug-fix release with a few non-critical bugs fixed since version 1.1 and with full support for JIRA 4.4.

New in Structure 1.1 (Jul 30, 2011)

  • Structure Panel on the Issue Page by default displays only the viewed issue, its parents and sub-issues, but not other issues from the hierarchy.
  • JIRA Administrator is now able to select which users can use Structure and create new structures.
  • Multiple smaller improvements, bug fixes and performance optimizations.
  • Preliminary version for JIRA 4.4.

New in Structure 1.0 (Jul 18, 2011)

  • Improvements:
  • GreenHopper synchronizer allows to select non-global Rank and Epic/Theme fields (enabled for the selected project.)
  • Progress column now shows numerical % value in the tooltip if you keep the mouse pointer over it.
  • Description column is added to the list of available columns, which lets you print description from the Structure's printable page.
  • Bundled synchronizers (GreenHopper and Links) now write synchronization undo files to offset the risk of massive unintended changes due to incorrect synchronizer configuration. The undo files may be processed by a script to reverse the changes to issue data.
  • Notable Bugs Fixed:
  • Server exception when many projects are enabled for Structure in the administration interface
  • Missing expand/collapse icons in the Internet Explorer 7
  • GreenHopper Synchronizer with "Force Sub-tasks" mode allows placing sub-tasks at incorrect positions in the structure
  • Text search does not find fully spelled words when indexing language is other than "other"