The Future of JIRA Agile
Announcement — Removal of Classic boards from JIRA Agile
Classic boards will be removed in JIRA Agile 6.7 (scheduled for April 2015). This means:
- JIRA Server — JIRA Agile 6.7 for JIRA Server will not include Classic boards.
- JIRA Cloud — Classic boards will be removed when JIRA Agile 6.7 is deployed.
We recommend that you migrate your projects to the new boards, as soon as possible.
We recommend that you migrate to the new board as soon as possible. The migration guide linked below will help you get a new board up and running. The guide also lists the main Classic board features and whether they are available via similar functionality in the new board.
We welcome customer feedback. If you'd like to contact us about this decision, please use the feedback form below.
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:
- GHS-7879 - Getting issue details... STATUS
- GHS-9689 - Getting issue details... STATUS
- GHS-3922 - Getting issue details... STATUS
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).
Comments disabled for this page
We still want your feedback, however, we have decided to disable comments on this page, so this feedback is consolidated into fewer channels. As mentioned at the top of the page, we'd love to hear your feedback via our feedback form.
If you have a specific feature request or bug report, you can still raise tickets for us in our issue tracker, via the buttons below. However, the feedback form is easier to use and our preferred method of receiving feedback as we approach the removal of Classic boards from JIRA Agile.
Use the buttons below to view issues related to this page, create a new issue or view the archive of old comments (PDF):
