The Future of JIRA Agile

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Background

The board you see today is a fresh start for JIRA Agile. We built it to take advantage of the latest in web technology and provide you, the customer, with an awesome experience for planning, tracking and reporting on the progress of your Agile projects and teams.

One thing is absolutely clear: your Agile project does not necessarily map to a single JIRA Project. For that reason we have addressed the most common feature request: GHS-1800 - Getting issue details... STATUS . Not being folks to sit still, we took this opportunity to introduce a new user experience with fewer page reloads and more useful URLs —  users can have a URL for the displayed page ( GHS-990 ).

 

On this page:

Related pages:

The new board is extraordinarily flexible due to our use of the JIRA Query Language (JQL) — you can show many projects or one project, based on whatever filter criteria you choose.

Furthermore, the board has returned the Fix Version field back to its intended use case, showing which versions a bug or story can be found in. The board has resulted in a decoupling of Sprints from the Fix Version field ( GHS-945 ). The Fix Version field is now available for release planning via the Versions panel in Plan mode.

We also have a new ranking field, Global Rank, which provides better performance than the previous solution. For the first time, you can now rank issues across JIRA Projects. With the introduction of the Global Rank, JIRA and JIRA Agile no longer need to reindex all of the issues in each JIRA Project every evening ( GHS-2727 ).


How is the new board different from the Classic Planning/Task/Chart/Released Boards?

The new board is very similar to the Classic Task Board with a few significant differences:

  • support for multiple JIRA projects
  • swimlanes
  • control chart for measuring the cycle time
  • interactive charts (zoom and click)
  • permanent links provide 'what you see is what they get' when emailing or IM'ing URLs
  • quick filters are based on JQL so you can create your own

Over time the new board will continue to evolve to replace the bulk of the functionality on the Classic Planning/Task/Chart/Released Boards.

The plan

The board (previously known as the "Rapid Board") graduated from Labs in GreenHopper 5.8, initially providing support for Kanban teams. Scrum functionality was then introduced in 5.8.5, and graduated from Labs in 5.10. Epics were added in  6.0.6 and graduated from Labs in 6.1. Versions were added in 6.1.4 and graduated from Labs in 6.2. In 6.0, we moved the existing boards (Planning, Task, Chart and Released Boards) to a Classic Mode, and dropped the "Rapid" title for the new board.

Our aim is to remove the Classic Boards functionality entirely in favour of the new board. We would like your feedback on whether there are issues that are stopping you from migrating. Check the tickets that have already been raised in our issue tracker (View issues button below) and add your comments and votes to them. If there isn't a ticket for your issue, raise one using the Create an issue button below and add a classic-migration label to it.

We assess each issue that is raised, although we cannot commit to fixing all of them. Currently, we consider the following issues to be blockers and will fix them before removing the Classic Boards:

What now?

If you haven't yet tried the new board, we encourage you to give it a go. Please note, contexts are replaced by boards; there is no migration path, so if you are already using JIRA Agile then you will need to recreate these from scratch.

 

Comments disabled for this page

We still want your feedback, however, we have decided to disable comments on this page in favour of issues in the JIRA Agile project on https://jira.atlassian.com.

Unlike other pages in our documentation, this page describes a decision to deprecate a feature (Classic Boards) in favour of a better feature (boards). As such, comments on this page are usually product feedback and are duplicated by tickets in the JIRA Agile project on https://jira.atlassian.com . Using one channel for tracking feedback about this change allows us to respond to you in a more timely manner.

Use the buttons below to view issues related to this page, create a new issue or view the archive of old comments (PDF):

Add a classic-migration label to your issue after you create it

 

 

 

Last modified on Apr 16, 2014

Was this helpful?

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