The Future of JIRA Agile

Classic boards removed from JIRA Agile

Classic boards have been removed in this release, JIRA Agile 6.7. This means:

  • JIRA Server — JIRA Agile 6.7 for JIRA Server does not include Classic boards and gadgets.
  • JIRA Cloud — Classic boards and gadgets have been removed from JIRA Cloud.

If you still need to migrate to the new board, see the migration guide (linked below). The guide also lists the main Classic board features and whether they are available via similar functionality in the new board.

How do I know if I am using a Classic board?

If you are not sure whether you are using a newer Agile board or an older Classic board, you can distinguish the two via the page URL. When viewing a newer Agile board, the URL of the page will include the word 'rapid' (e.g. RapidBoard.jspa?rapidView=524) whereas a Classic board will not.

Background on this decision

In early 2012, we introduced the board that you see in JIRA Agile today. 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.

As we have advised since early 2013, our plan has been to eventually remove the Classic boards in favour of the new Agile board. We have been working closely with customers to make sure that the usage of the original Classic boards is covered by the new Agile boards. This includes implementing fixes for these three blockers (in JIRA Agile 6.6) as promised:

  • JSW-7879 - As a GH User, it would be great to show assignee's name in Rapid Board. Closed
  • JSW-9689 - Support preassigning work to specialists Closed
  • JSW-3922 - As a user, I would like to configure the cards displayed in the rapid board Closed

About the new board

One thing was absolutely clear in your feedback about Classic boards: your Agile project does not necessarily map to a single JIRA Project. For that reason, the new board addresses the most common feature request: support for multiple projects within JIRA Agile (GHS-1800). Not being folks to sit still, we also took the 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).

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 the Backlog.

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).

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport