7.3.4 (Security release)

Update of third-party libraries. Please read the security bulletin for more information.

7.3.3

7.3.2 (Security release)

The URL parameters for "Dependency Table by Jql" have been protected against possible XSS attacks. Please read the security bulletin for more information.

7.3.1 (Security release)

Dependency Table by Jql ("View on - Dependency Table" option of the Tree View menu ) has been protected against possible XSS attacks. Please read the security bulletin for more information.

7.3.0

7.2.3

7.2.2

7.2.1

7.2.0

7.1.2

7.1.1

7.1.0 

7.0.0 (Major release)

6.1.1 (Security fix)

The atl_token is now required from a lot of locations to prevent CSRF attacks. Please read the security bulletin for more information.

6.1.0

NEW: New option Export to Pivot Table available on the Tree view menu: it loads the current visible issues from the Tree view into a Pivot Table view for further analytics. In this way, it is very straightforward to analyze Epic & Portfolio hierarchies (or whatever issue) from a lot of dimensions.


6.0.0 (Major release)

5.4.2

5.4.1


MATRIX 100x100
BrowserTime Old VersionTime New VersionImprovement
Chrome10-11 s7-8 s3s
Mozilla9-10 s6-7 s3s
Opera10-11 s7-8 s3s
Edge17-20 s10-11 s7-9 s
IE23-24 s15-16 s8-9 s

5.4.0

5.3.4

5.3.3

5.3.2

5.3.1

5.3.0

Example:

Jira Software supports a link type named Issue Split to split stories into new ones,


In this dialog, the SSP-1 issue is going to be split into "One" and "Two"


This is how the split issues are displayed by default:



The new "one" and "two" children are linked in the outward direction. They do not contribute to their parent.

Thanks to this new feature, Jira administrators can reverse the link behavior in the app (they will continue working in the default mode in the resto of Jira):

When the link type is reversed, the inward and the outward directions are switched right within the app. This makes the children contribute progress to their natural parents:

Note that the "split from" (inward direction) overtakes the "split to" (outward direction) when they are displayed.

5.2.0

5.1.1

This affects the issues with bifurcations contributing to other issues by more than one way. IN the example below, the DEMO-4 issues blocks the DEMO-2 and the DEMO-3 issues.


The previous versions cared about the root only causing inconsistency in the intermediate levels: 

See how the DEMO-4 issue contributes to the root via the DEMO-2 issue only (100% contribution) and none via de DEMO-3 issue (0% contribution). However, the DEMO-4 issue is inconsistent as it is completed with 100% progress first., and no progress later.


Now, this has been improved by displaying consistency among all the issues:


See how that the DEMO-4 is 100% resolved in both places and it contributes in a balanced way: 50% via the DEMO-2 and 50% via the DEMO-3 issues. And the link is painted with orange color to highlight a partial/balanced contribution.

Whereas the calculation is the same from the root issue perspective, now everything is more coherent and easy to understand. 


5.1.0

5.0.7

5.0.6

5.0.4

5.0.0 

4.3.0

4.2.2

4.2.1

4.2.0 Support for gadgets


4.1.12 Support for performance setting tuning

4.1.11 Maintenance release

4.1.10a Fix error in Agile Dashboards (and Blank Tree and Network Graph views)

There was a conflict with one variable name. We have changed the name in hundred places in version 4.1.10, tested the app etc. Unfortunately, the name was not replaced in one line causing the tree and network views gone broken. This release fixes both issues: the agile Board error and the Tree and Network blank views. Apologies for the inconveniences.


4.1.9 Fix: Export to Excel results in 404 HTTP Error

A new configuration parameter (Jira local Url) is supported to avoid to configure domain names resolutions to export to Excel. Please read the Install and Configure documentation for more details.


4.1.8 Fix: Error panel in tree hierarchy view


4.1.7 (cumulative changes since the 4.0.19 version)