JIRA Agile 6.3.12 Release Notes

 7 April 2014

The Atlassian team announces the release of JIRA Agile 6.3.12. This point release contains a number of features as well as several updates and fixes. Upgrading to JIRA Agile 6.3.12 is free to all customers with active JIRA software maintenance.

Highlights

Labs: Enhanced reports — Release Burndown

We're overhauling the existing reports in JIRA Agile. Over the next few releases, we will be progressively introducing enhanced versions of a number of the reports via Labs. To opt in for these new reports, enable Enhanced Reports in Labs.

In this release, we've introduced a new chart: the Release Burndown. If you have used the Version Report before, you will notice some similarities, as the Release Burndown also tracks your team's progress towards the completion of the work for a release (version).

The Release Burndown makes tracking much easier though, as it is optimised for Scrum teams that work in sprints. We've designed it as a bar chart 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 your release, based on your team's velocity.

Read more...

Improvements to reports

We've made a number of minor improvements to reports in JIRA Agile:

  • A "status spinner" will show when a report is loading/re-loading or retrieving data from the server (this is for all reports). A "Chart updated" message will briefly display after the report has completed loading (this is for Enhanced reports, available via Labs).
  • Internationalisation for dates and numbers: the appropriate date/number format for the user's locale is now used in Enhanced reports (available via Labs).

New code integration features for issues

If you are using JIRA Agile with JIRA 6.2 or later, the new Development panel will be shown on every issue. This panel helps you to evaluate the development status of an issue at a glance. If you need to investigate further, click any item to display more details, or drill down into the development tool.

Connect JIRA to one of these compatible applications to enable the following:

  • Bitbucket view and create branches, view commits, view and create pull requests
  • FishEye/Crucible (Git/Subversion/Perforce/CVS): view branches, view commits, view and create reviews
  • Bamboo: view the status of builds and deployments
  • GitHub/GitHub Enterprise: view branches, view commits, view and create pull requests

Learn more (JIRA documentation): Streamlining your development with JIRA

Upgrading JIRA Agile

What do I do if I have problems with JIRA Agile?

If you run into problems when installing/upgrading JIRA Agile or using it after an upgrade, please contact our support team. This is the fastest way to get your problems addressed. The support team can work with you to figure out what is going wrong, and if there is a bug with JIRA Agile, they will escalate it to our development team.

General upgrade notes

Before upgrading, please read the JIRA Agile 6.3 Upgrade Notes.

  • If you are using JIRA Agile with JIRA Server, upgrade via the JIRA Plugin Manager.
    • Note, if your JIRA instance cannot access the internet, download the add-on separately (from the Atlassian Marketplace) and install the add-on file by upload, as described here: Installing Add-ons.
  • If you are using JIRA Agile with JIRA Cloud, subscribe to our blog for the latest updates (see this page for instructions). Please note that JIRA Agile may be released for JIRA Server several days before it is updated for JIRA Cloud. To find out what version of JIRA Agile is running in JIRA Cloud, see Application Versions.

Updates and Fixes in this release

JIRA Agile 6.3.12 includes the following updates and bug fixes:

T Key Summary
Loading...
Refresh

^top

Last modified on Jul 1, 2014

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.