View Source

These release notes are intended for our EAP program members. We assume that you have read previous documentation on Structure.Gantt. If not, please start by checking out Structure.Gantt Quick Start Guide, and release notes for the previous versions.

New features

Gantt Chart Wizard, which helps users get started and quickly build their first gantt chart.
Automatic scheduling of closed issues based on the Resolution date.
A number of performance improvements.

See below for detailed information on each feature.

Installation

Structure.Gantt 1.0 requires Structure 4.5 or later. Jira 7.2 - 7.6 are supported.

Until Structure.Gantt is available on the Atlassian Marketplace, it should be installed via file upload (Administration | Add-ons | Manage add-ons | Upload add-on).

Upgrading

If you already have production data on Gantt, please backup your database or Jira before upgrading.

Please review your Gantt configuration after upgrading to check that your settings remain the same. Also there is the new Resolution Date scheduling option, which is enabled by default.

New Features in Details

Gantt Chart Wizard

We have created a wizard to help new users get started and build their first Gantt chart in just a few minutes. The first few steps allow to define the structure - the scope and the hierarchy based on Jira, Epic and Portfolio links and sub-tasks. Then you can quickly define the essential Gantt configuration settings such as fields for manual scheduling, links for dependencies and the attribute for resources.

Once you complete all the steps, the wizard will create a new structure, its new view and a corresponding Gantt configuration.

Resolution Date as Finish Date

This is the new option in the Scheduling section. When it's enabled, all resolved tasks that are not scheduled manually, will be scheduled using their resolution date as the Finish Date.

Known issues

Below are a few known issues and non-obvious cases.

If you are working with issues in multiple time zones they may be aligned slightly off on the timeline. This may result in a small error in the calculation of the parent issue dates (if grouping is used) or may lead to an issue being excluded from the critical path, because this deviation adds a small slack between the issues.
If a formula is selected as the source for resource assignment, any changes made to this formula after the resource list has been built, will be ignored. For example, if your formula had a variable assigned to one field and you reassign variable to another field after the resource list has already been built, the resource list will not be updated to reflect this change.
Bars visibility depends on the permissions of the structure owner (not just the current user). This means that if the structure owner cannot see some issues you are working with, you won't be able to see them on the Gantt chart.
If you are migrating from the Gantt Beta, the tasks that are assigned to a resource with the capacity higher than 1 will now take longer. That's because we have introduced the Maximum Units parameter, which tells what maximum number of resource units can be used for the task and it is set to 1 by default.
Default task duration for newly created configs is now 1 day (was 1 hour).