JIRA Agile 6.5 Release Notes
18 August 2014
Reporting is a crucial part of any Agile development project. Good reports can help you plan more effectively and keep your team on track.
Over the past few releases, we have progressively introduced enhanced reports via Labs. We're proud to announce that these reports have graduated from Labs in this release, and are now production-ready. Read about the new reports below.
New features in this release
New Release Burndown report
The new Release Burndown helps you track your team's progress towards the completion of the work for a release (version). It is optimised for Scrum teams that work in sprints (as opposed to the Version report). We've designed it as a bar chart that helps you see exactly what is happening in each sprint. The chart also predicts the number of sprints that are required to finish the remaining work in the release, based on your team's velocity.
New Epic Burndown report
Another new chart introduced in this release is the Epic Burndown. This report tracks your team's progress towards the completion of the work for an epic.
The Epic Burndown is similar to the Release Burndown. It is optimised for Scrum teams that work in sprints (as opposed to the Epic report), and has a bar chart design that helps you see exactly what is happening in each sprint, such as work completed and scope changes. The chart also predicts the number of sprints that are required to finish the remaining work in the epic, based on your team's velocity.
Enhanced Control Chart
The Control Chart lets you see the cycle time of issues over time. We've completely overhauled this chart in this release, making it even easier for you to analyse your team's performance.
You'll find a range of design and usability improvements, such as better chart controls, issue clustering and a 'How to read this chart' section to help you understand how to use it. We've made changes under the covers as well, including improving the way the rolling average is calculated, and basing the standard deviation on the rolling average instead of the overall average.
Release Burndown and Epic Burndown: More informative forecasts
We have redesigned forecasts in the release burndown and epic burndown reports. It's now easier to distinguish predicted sprints from completed sprints. A new dialog provides you with more information about the predicted work for your release or epic.
Assignees shown on boards in Plan mode
Boards now show the assignees for issues in Plan mode (note, Work mode already shows assignees), making it easier for you to understand the workload of each team member:
- For issues: the assignee's profile picture is shown on the card.
- For sprints: the sprint header displays the profile pictures for the assignees of all issues in the sprint. A handy tooltip for each picture shows a summary of the work assigned to the user.
Click to learn more about the other new features and improvements in JIRA Agile 6.5:
- Control chart only shows Swimlanes configuration if your board uses JQL swimlanes — Swimlanes configuration is only valid if your board uses JQL swimlanes, so this change prevents users getting confused by incorrectly configuring the chart.
- Clicking a card automatically opens the issue detail view — Previously, clicking a card would select it, but not open the issue detail view. You can still select a card without opening the issue view by using cmd/shift-click.
- Data table in Release/Epic burndown now shows work completed before first sprint — If issues are completed before the first sprint, the data table will now show information about the issues.
Updates and fixes in this release
6.5.0 — 18 August 2014
This is the first 6.5.x version made available for download.
The JIRA Agile 6.5 team
Michael Tokar (team lead)
Michael Andreacchio (team lead)
Chung Park Chan
Davy Sjauw Mook
James Giles IV
Jeff Curry (team lead)
Joe Wai Tye
John Chin Kim Loong
Matthew Hunter (team lead)
Yew Teck En
Zulfadli Noor Sazali
Was this helpful?
Thanks for your feedback!