Migrating from Classic Boards
Classic boards have been removed in this release, JIRA Agile 6.7
See The Future of JIRA Agile for more details.
If you need help migrating your projects to the new boards, try getting in touch with an Atlassian Expert.
Watch this page. Further information about features and workarounds may be added over time.
This page provides instructions on how to migrate from a Classic board to a new board.
We are aware that the lack of certain features in JIRA Agile may make it difficult for some customers to migrate. These features have been listed on this page with information on their availability in JIRA Agile and any workarounds.
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.
Migrating from a Classic board to a new board
Migrating from a Classic board to a new board in JIRA Agile is a manual process. This section describes a basic scenario for migrating from a Classic board to a new board in a Scrum project. To do this, you will create a board and configure it so that it works in a similar (or better) way to your Classic board.
Many teams use different features of the Classic board, so these instructions don't cover every configuration: read Feature availability in JIRA Agile for details on each feature's availability and workarounds. These instructions are also targeted at customers using Scrum. If you use Kanban, then many of the steps below will not apply to you (e.g. creating sprints).
1. Create a new board(s) in the same project as your Classic board.
Create a new Scrum Board or a Kanban Board — pick the option that fits your team's needs. Note, a Classic board is based on a single project. However, a new board can be based on many projects (and vice versa, a project can have many boards that reference it). This is useful for when you want to manage work for multiple related projects in one place.
Mapping your Classic board contexts to a new board:
- As a general rule, you should map each of your Classic board contexts to a new board and configure the board's filter to match the context. This is usually the case when you have used contexts to manage separate backlogs for different teams or project components.
- In some cases, you may want to use a Quick Filter rather than create a new board. For example, if you are using a context to quickly switch between different issue types (e.g. show only bugs) or to show team-specific views of a common backlog, it would be better to create a Quick Filter.
- Classic board contexts permitted sorting by different fields. The new boards will only order by Rank (if ranking is enabled). We recommend that you don't order by a different field, as a number of features won't work (e.g. ranking, sprints, etc).
For instructions, see Creating a Board, Configuring Filters and Configuring Quick Filters. Once you have created and configured your new board, all of the issues should be in the backlog.
2. Re-rank and flag your issues
The new boards only use the 'Rank' custom field to rank issues. This is the same 'Rank' field used by Classic boards. If you have used a field other than the 'Rank' custom field, you will need to manually re-rank your issues. For instructions, see Ranking an Issue.
Similarly, the new boards only use the 'Flagged' custom field to flag issues. This is the same 'Flagged' field used by Classic boards. However, if you have used a field other than the 'Flagged' custom field, you will need to manually re-flag your issues. Note, the new boards only have one type flag. For instructions, see Flagging an Issue.
3. Create sprints in your project
Sprints are standalone objects in the new boards, as opposed to "sprints" in Classic boards which are based on JIRA versions. If you used versions to represent sprints in your Classic board, use sprints in the new board instead. For instructions, see Creating a Sprint.
Note, as Classic board "sprints" are based on JIRA versions, you can always view historical information about them via the Version Report in the Agile boards.
4. Assign issues to sprints
For instructions, see Adding an Issue to a Sprint.
Tip: To check whether the issues in your project have been mapped to the appropriate sprints, view the issues for your project by going to Projects > (your project) > Issues > All issues > 
> List View. Customise the search results to show the Sprint and Fix Version fields — look for issues without a Sprint value, or issues where the Sprint value doesn't match the Fix Version.
5. Customise cards and configure the issue detail view for your board(s)
The "cards" in new boards do not show the same level of detail as cards in Classic boards, as they are optimised to show information in the Issue Detail View of the board. Click on any card in a new board to show the detailed view of the issue.
However, you can add up to three additional fields to cards. These can be different fields for the Backlog versus the Active sprints. See Customising Cards. You can also configure the issue detail view to reflect the information shown on your Classic board cards. See Configuring the Issue Detail View for instructions.
6. Other changes
Here are a few other change that you may need to make:
- Configure non-working days for your board(s) — the global non-working days configuration will be used by the new board, but you will need to re-configure any board-specific non-working days for your new board(s). See Configuring Working Days for instructions.
- Configure gadgets for your dashboard — The Classic gadgets will be retired when the Classic boards are retired. JIRA Agile has a number of gadgets that provide similar functionality to the Classic gadgets. See the Gadgets section below.
Need help?
If you need help migrating from Classic boards, visit our Support System and create a support request. You will need to create an account on the Support System, if you don't have one already.
See Getting Help for other help resources.
Feature availability in JIRA Agile
We want your feedback!
We would love to hear from you if you need one (or more) of the features in the list below. Just add a comment to the related issue(s) linked below and describe your use-case. Feel free to watch and vote for the issue too.
If you have any other questions or comments, please use this feedback form.
In this section:
Versions
Gadgets
Classic gadgets will be retired when Classic boards are retired.