JIRA Agile 6.6 Release Notes

 

_{8 September 2014}

JIRA Agile 6.6 ships with the most popular feature request in our backlog, custom cards, as well as a new sprint workload summary. If you are using Classic boards in JIRA Agile, make sure that you read our announcement about Classic boards below.

 

_{JIRA Agile 6.6 Upgrade Notes}

New features in this release

Custom cards

The ability to customise cards is the most popular feature request for JIRA Agile (GHS-3922). Want your team to see the Due Date, Components or other fields on cards? You can now bring the right information to your team's attention, rather than relying upon people having to view the issue details for individual issues. 

You can add up to three additional fields to cards. These can be different fields for Plan mode versus Work mode. Go to Board layout in your board's configuration to try it out.

Learn more... 

Sprint workload summary

In JIRA Agile 6.5, we introduced the ability to see the assignees for issues on Plan mode of boards. This release includes a handy workload summary for each sprint that allows you to identify the workload for specialists in a Scrum team and plan accordingly. 

Announcement: End of life for Classic Boards

In the previously published The Future of JIRA Agile, we have described how we intended to eventually remove Classic Boards from JIRA Agile. We are announcing that JIRA Agile 6.6 will be the last major version to ship with Classic boards. This means:

• JIRA Server — The next major release of JIRA Agile for JIRA Server will not include Classic boards. This will ship no sooner than 60 days from the date of the JIRA Agile 6.6 release.
• JIRA Cloud — Classic boards will be removed from JIRA Cloud in the next major upgrade of JIRA Agile (no sooner than 60 days from the date of the JIRA Agile 6.6 upgrade).

With the current board, introduced two years ago in JIRA Agile (GreenHopper) 6.0, we believe that we have a replacement that is simple, powerful and helps you to deliver higher quality products faster. We have also worked closely with customers to make sure that the usage of the original Classic boards is covered by the new Agile boards.  

Change is never easy and we fully understand that the removal of Classic boards may impact your team’s usage of JIRA Agile. For this reason, we have created a migration guide to assist with the transition. We strongly urge you to begin your team's migration as soon as possible.

The JIRA Agile 6.6 team