JIRA Agile 6.4 Release Notes
Customers with large scale instances: Do not upgrade to JIRA Agile 6.4.x, 6.5.x or 6.6.0. Upgrade to JIRA Agile 6.6.13 instead.
JIRA Agile 6.4 (with JIRA 6.2 or later) provides more code-related information in your issues, that you can assess and action. Create a branch, see commits and pull requests, watch builds, and more!
Important
This is a major upgrade. We have made a number of changes under the covers that you need to be aware of before you upgrade. Please read the JIRA Agile 6.4 Upgrade Notes (linked above) and note the upgrade tasks, in particular, the changes to the Rank field.
New features in this release
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
Labs: Enhanced reports — Epic 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 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, 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.
Who closed that sprint?
If you've ever wanted to find out who closed a particular sprint, you can now see this on the Burndown Chart and Sprint Report.
Sprint Report
Burndown Chart (data table)
Inline issue creation (with JIRA 6.3)
If you are using JIRA Agile 6.4 with JIRA 6.3 or later, you can now create an issue from within your Scrum board during planning. Just click the Create issue link, fill in the details and hit the Enter button. The new issue will be automatically added to your backlog.
Updates and fixes in this release
We have released a number of 6.4.x versions to fix critical issues found in JIRA Agile. Minor versions usually have additional features, however each of the versions shown below have the same set of features.
See the version history below for details on each of minor release, or view the full list of issues fixed across all 6.4.x versions.
6.4.5 — 2 September 2014
AVAILABLE
This is the current version available for download. 6.4.5 also fixes issues affecting ranking.
6.4.4 — 12 August 2014
REMOVED
This version is not available for download anymore, as it is superseded by 6.4.5. 6.4.4 fixes a critical issue affecting ranking.
6.4.3 — 23 July 2014
REMOVED
This version is not available for download anymore, as it is superseded by 6.4.4. 6.4.3 fixes a critical issue affecting Oracle databases.
6.4.2 — 4 July 2014
REMOVED
This version is not available for download anymore, as it is superseded by 6.4.3. 6.4.2 was released to fix a number of critical issues affecting upgrades, issue creation and ranking issues.
6.4.0.9 — 27 June 2014
REMOVED
This version is not available for download anymore, as it was superseded by 6.4.2. 6.4.0.9 was released to fix a critical issue affecting Oracle databases.
6.4.0.8 — 25 June 2014
REMOVED
This version is not available for download anymore, as it was superseded by 6.4.0.9. 6.4.0.8 was released to fix critical issues affecting re-indexing, and SQL Server 2005 and Oracle databases. Note, 6.4.0.6 was not made available to the public — 6.4.0.8 includes fixes tagged for 6.4.0.6.
6.4.0.3 — 2 June 2014
REMOVED
This was the first 6.4.x version made available for download. It is not available for download anymore as it was superseded by 6.4.0.8. 6.4.0.3 includes a number of fixes to bugs present in 6.3.13.1 and earlier versions (see list below for details).
Notable features from the 6.3.x releases
JIRA Agile 6.4 bundles up all of the features introduced in the 6.3.x releases. If you haven't been using any of the 6.3.x releases, here's what you've missed.
JIRA Agile and Confluence — Better together
If you use JIRA Agile and Confluence together, you can now create and/or link Confluence pages to JIRA Agile epics, stories and sprint reports. Read our solutions guide and try doing the following in JIRA Agile.
-
From an epic: Create a new requirements document in Confluence (via the Product Requirements blueprint), or link to an existing page. -
From a sprint: Create new meeting notes in Confluence (via the Meeting Notes blueprint), or link to an existing page. -
From a sprint report: Create new retrospective notes in Confluence (via the Retrospectives blueprint), or link to an existing page.
Labs: Enhanced reports — New Control Chart and Release Burndown
We've redesigned the Control Chart and introduced the Release Burndown, as part of our reports overhaul. To opt in for these new reports, enable Enhanced Reports in Labs.
-
Control Chart: The new Control Chart introduces a range of design and useability 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 an improvement to the way the rolling average is calculated, and basing the standard deviation on the rolling average instead of the overall average. Learn more...
-
Release Burndown: The 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. Learn more...
Improvements to the Sprint field
We've made two big improvements to the Sprint field in this release. Firstly, the Sprint field now shows the sprint name, not the sprint ID. When editing the field, you can also search for a sprint by name and JIRA Agile will suggest matching sprints (with sprints from boards /issues that you've recently viewed shown first).
Secondly, the Sprint field is now enabled by default and displays on the create/edit/view issue screens (users may need to show the field on the 'Create Issue'/'Edit Issue' dialog via Configure Fields). You won't have to mess around with your screen configurations to start using this field.
Board administrators
A board can now have multiple board administrators , instead of a single owner. When you configure a board, you will be able to add multiple groups and users. Any users specified in the Board Administrators field (individually or via a group) will have all of the same permissions as the owner field in previous versions of JIRA Agile. Learn more...
Status lozenges
JIRA Agile now uses status lozenges to represent issue status rather than text/icons. The new status lozenges make it easier for you to see an issue's status at a glance, and look great! The lozenges also conform to the Atlassian Style Guidelines.
You can also choose a Category when creating a status in the simplified workflow editor (board must be using the Simplified Workflow). The category sets a colour for the status lozenge.
Note, JIRA 6.2 or later is required for this feature.
"First initial" avatars
JIRA Agile now uses the first initial of your full name (not username) as your avatar, if you do not want to upload an image or photo. This makes it easier for users to identify who is associated with an issue, at a glance, when custom images are not used. You will see these avatars on your boards (Work mode) and on the Agile wallboard gadget.
And more!
-
Improvements to the Sprint Health gadget — Click any of the statistics on the Sprint Health gadget to drill down to detailed information on that statistic. For example, click Blockers in the gadget and you will be shown the search for blockers for the sprint.
-
Add an issue to a sprint directly from Work mode: any issue (or issues) created during a sprint on Work mode can now be added directly to that sprint.
-
Tooltip guidance when you can't create or start a sprint — Ever wondered why a Create sprint or Start sprint button/link is disabled on your board in Plan mode? You can now hover over either of these controls and a tooltip will show you exactly why it is disabled (e.g. you are not an administrator for the project, there is an active sprint).
-
Quick Filters list in Plan/Work mode can be collapsed — Quick Filters are now rolled up into a single line, rather than spanning multiple lines. You can click the Show more link to show all filters and you can collapse them into a single line again via the Show less link. -
See board type (Scrum or Kanban) on the Manage Boards screen — You can now determine the type of each board when viewing them on Manage Boards screen.
-
Improved board configuration user interface — We've updated the board configuration user interface with a number of improvements. You'll notice that the tabs have been moved into a menu on the left. We've also made a number of tweaks to clean up the Columns configuration screen.
-
More accessible reports — Report mode now lists all available reports on the screen, instead of hiding them in a dropdown menu.
-
Hide/Show header control moved — The control for hiding/showing the header has been moved up next to the Plan, Work, Report and Board controls, rather than next to the Quick Filters. -
A more discreet give feedback button — The Give feedback button won't clutter your view in JIRA Agile anymore. We still love hearing your feedback, but we've made the button a little less inconspicuous, so it doesn't get in your way.
The JIRA Agile 6.4 team
Development
Michael Tokar (team lead)
Michael Elias
Ivo Bosticky
David Tang
Jason Sheehy
Ian Dick
Patrick Teen
Jonathan Raoult
Product Management
Martin Jopson
Marketing
Dan Radigan
Jake Brereton
Cross-product
Design
Brendan Humphrey
Dean Hudson
QA
Kiran Shekhar
Technical Writing
Andrew Lui
Support
Michael Andreacchio (team lead)
Ahmad Danial
Ala Al-Shargabi
Andre Petry
Anna Cardino
Bejoy Jaison
Benito Picarelli
Bruna Griebeler
Clarissa Gauterio
Chung Park Chan
Daniel Leng
Danilo Conrad
Daryl Chuah
David Currie
David Mason
Dave Nicholson
Davy Sjauw Mook
Daniel Watania
Dobroslawa Wierzbicka
Gan VoonKiat
Gary Sackett
Ivan Maduro
James Giles IV
Janet Albion
Jason Worley
Jeff Curry (team lead)
Joe Wai Tye
John Chin Kim Loong
Julian Rahmadiputra
Support
Luciano Fagundes
Mauro Badii
Marcus Almeida
Matheus Fernandes
Matthew Hunter (team lead)
Melissa Klingler
Michael Thai
Mick Nassette
Muhammad Fahd
Nick Mason
Richie Gee
Ruchi Tandon
Shannon Mackie
Paul Greig
Pedro Cora
Pedro Souza
Pietro Schaff
Taiwo Akindele
Vicky Kharisma
Viet Dung
Yew Teck En
Zulfadli Noor Sazali
JIRA Agile 6.6 Release Notes
JIRA Agile 6.4 (with JIRA 6.2 or later) provides more code-related information in your issues, that you can assess and action. Create a branch, see commits and pull requests, watch builds, and more!
Important
This is a major upgrade. We have made a number of changes under the covers that you need to be aware of before you upgrade. Please read the JIRA Agile 6.4 Upgrade Notes (linked above) and note the upgrade tasks, in particular, the changes to the Rank field.
New features in this release
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
Labs: Enhanced reports — Epic 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 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, 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.
Who closed that sprint?
If you've ever wanted to find out who closed a particular sprint, you can now see this on the Burndown Chart and Sprint Report.
Sprint Report
Burndown Chart (data table)
Inline issue creation (with JIRA 6.3)
If you are using JIRA Agile 6.4 with JIRA 6.3 or later, you can now create an issue from within your Scrum board during planning. Just click the Create issue link, fill in the details and hit the Enter button. The new issue will be automatically added to your backlog.
Updates and fixes in this release
We have released a number of 6.4.x versions to fix critical issues found in JIRA Agile. Minor versions usually have additional features, however each of the versions shown below have the same set of features.
See the version history below for details on each of minor release, or view the full list of issues fixed across all 6.4.x versions.
6.4.5 — 2 September 2014
AVAILABLE
This is the current version available for download. 6.4.5 also fixes issues affecting ranking.
6.4.4 — 12 August 2014
REMOVED
This version is not available for download anymore, as it is superseded by 6.4.5. 6.4.4 fixes a critical issue affecting ranking.
6.4.3 — 23 July 2014
REMOVED
This version is not available for download anymore, as it is superseded by 6.4.4. 6.4.3 fixes a critical issue affecting Oracle databases.
6.4.2 — 4 July 2014
REMOVED
This version is not available for download anymore, as it is superseded by 6.4.3. 6.4.2 was released to fix a number of critical issues affecting upgrades, issue creation and ranking issues.
6.4.0.9 — 27 June 2014
REMOVED
This version is not available for download anymore, as it was superseded by 6.4.2. 6.4.0.9 was released to fix a critical issue affecting Oracle databases.
6.4.0.8 — 25 June 2014
REMOVED
This version is not available for download anymore, as it was superseded by 6.4.0.9. 6.4.0.8 was released to fix critical issues affecting re-indexing, and SQL Server 2005 and Oracle databases. Note, 6.4.0.6 was not made available to the public — 6.4.0.8 includes fixes tagged for 6.4.0.6.
6.4.0.3 — 2 June 2014
REMOVED
This was the first 6.4.x version made available for download. It is not available for download anymore as it was superseded by 6.4.0.8. 6.4.0.3 includes a number of fixes to bugs present in 6.3.13.1 and earlier versions (see list below for details).
Notable features from the 6.3.x releases
JIRA Agile 6.4 bundles up all of the features introduced in the 6.3.x releases. If you haven't been using any of the 6.3.x releases, here's what you've missed.
JIRA Agile and Confluence — Better together
If you use JIRA Agile and Confluence together, you can now create and/or link Confluence pages to JIRA Agile epics, stories and sprint reports. Read our solutions guide and try doing the following in JIRA Agile.
- From an epic: Create a new requirements document in Confluence (via the Product Requirements blueprint), or link to an existing page.
- From a sprint: Create new meeting notes in Confluence (via the Meeting Notes blueprint), or link to an existing page.
- From a sprint report: Create new retrospective notes in Confluence (via the Retrospectives blueprint), or link to an existing page.
Labs: Enhanced reports — New Control Chart and Release Burndown
We've redesigned the Control Chart and introduced the Release Burndown, as part of our reports overhaul. To opt in for these new reports, enable Enhanced Reports in Labs.
- Control Chart: The new Control Chart introduces a range of design and useability 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 an improvement to the way the rolling average is calculated, and basing the standard deviation on the rolling average instead of the overall average. Learn more...
- Release Burndown: The 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. Learn more...
Improvements to the Sprint field
We've made two big improvements to the Sprint field in this release. Firstly, the Sprint field now shows the sprint name, not the sprint ID. When editing the field, you can also search for a sprint by name and JIRA Agile will suggest matching sprints (with sprints from boards /issues that you've recently viewed shown first).
Secondly, the Sprint field is now enabled by default and displays on the create/edit/view issue screens (users may need to show the field on the 'Create Issue'/'Edit Issue' dialog via Configure Fields). You won't have to mess around with your screen configurations to start using this field.
Board administrators
A board can now have multiple board administrators , instead of a single owner. When you configure a board, you will be able to add multiple groups and users. Any users specified in the Board Administrators field (individually or via a group) will have all of the same permissions as the owner field in previous versions of JIRA Agile. Learn more...
Status lozenges
JIRA Agile now uses status lozenges to represent issue status rather than text/icons. The new status lozenges make it easier for you to see an issue's status at a glance, and look great! The lozenges also conform to the Atlassian Style Guidelines.
You can also choose a Category when creating a status in the simplified workflow editor (board must be using the Simplified Workflow). The category sets a colour for the status lozenge.
Note, JIRA 6.2 or later is required for this feature.
"First initial" avatars
JIRA Agile now uses the first initial of your full name (not username) as your avatar, if you do not want to upload an image or photo. This makes it easier for users to identify who is associated with an issue, at a glance, when custom images are not used. You will see these avatars on your boards (Work mode) and on the Agile wallboard gadget.
And more!
- Improvements to the Sprint Health gadget — Click any of the statistics on the Sprint Health gadget to drill down to detailed information on that statistic. For example, click Blockers in the gadget and you will be shown the search for blockers for the sprint.
- Add an issue to a sprint directly from Work mode: any issue (or issues) created during a sprint on Work mode can now be added directly to that sprint.
- Tooltip guidance when you can't create or start a sprint — Ever wondered why a Create sprint or Start sprint button/link is disabled on your board in Plan mode? You can now hover over either of these controls and a tooltip will show you exactly why it is disabled (e.g. you are not an administrator for the project, there is an active sprint).
- Quick Filters list in Plan/Work mode can be collapsed — Quick Filters are now rolled up into a single line, rather than spanning multiple lines. You can click the Show more link to show all filters and you can collapse them into a single line again via the Show less link.
- See board type (Scrum or Kanban) on the Manage Boards screen — You can now determine the type of each board when viewing them on Manage Boards screen.
- Improved board configuration user interface — We've updated the board configuration user interface with a number of improvements. You'll notice that the tabs have been moved into a menu on the left. We've also made a number of tweaks to clean up the Columns configuration screen.
- More accessible reports — Report mode now lists all available reports on the screen, instead of hiding them in a dropdown menu.
- Hide/Show header control moved — The control for hiding/showing the header has been moved up next to the Plan, Work, Report and Board controls, rather than next to the Quick Filters.
- A more discreet give feedback button — The Give feedback button won't clutter your view in JIRA Agile anymore. We still love hearing your feedback, but we've made the button a little less inconspicuous, so it doesn't get in your way.
The JIRA Agile 6.4 team
Development
Michael Tokar (team lead)
Michael Elias
Ivo Bosticky
David Tang
Jason Sheehy
Ian Dick
Patrick Teen
Jonathan Raoult
Product Management
Martin Jopson
Marketing
Dan Radigan
Jake Brereton
Cross-product
Design
Brendan Humphrey
Dean Hudson
QA
Kiran Shekhar
Technical Writing
Andrew Lui
Support
Michael Andreacchio (team lead)
Ahmad Danial
Ala Al-Shargabi
Andre Petry
Anna Cardino
Bejoy Jaison
Benito Picarelli
Bruna Griebeler
Clarissa Gauterio
Chung Park Chan
Daniel Leng
Danilo Conrad
Daryl Chuah
David Currie
David Mason
Dave Nicholson
Davy Sjauw Mook
Daniel Watania
Dobroslawa Wierzbicka
Gan VoonKiat
Gary Sackett
Ivan Maduro
James Giles IV
Janet Albion
Jason Worley
Jeff Curry (team lead)
Joe Wai Tye
John Chin Kim Loong
Julian Rahmadiputra
Support
Luciano Fagundes
Mauro Badii
Marcus Almeida
Matheus Fernandes
Matthew Hunter (team lead)
Melissa Klingler
Michael Thai
Mick Nassette
Muhammad Fahd
Nick Mason
Richie Gee
Ruchi Tandon
Shannon Mackie
Paul Greig
Pedro Cora
Pedro Souza
Pietro Schaff
Taiwo Akindele
Vicky Kharisma
Viet Dung
Yew Teck En
Zulfadli Noor Sazali