Choose this option if your team wants the added flexibility of scheduling next-gen epics on the roadmap. You will need to specify a Jira issue link type that links both classic and next-gen issues to Roadmap issues:

Create or edit a Program

• Next-gen boards can be added to a new or existing program - this includes next-gen boards set up as scrum or kanban

• A next-gen board can be used as the Roadmap board. This is because you have specified the issue linking type

Create an Increment

A next-gen board can’t be used for global/shared sprints.

Reason - Completing a sprint that contains both classic and next-gen issues on a next-gen board will not roll classic issues into the next sprint.

When creating a new increment, you won’t be able to select a next-gen board for shared sprints. This is because completing a sprint that contains both classic and next-gen issues on a next-gen board will not roll classic issues into the next sprint.

Please be aware that shared sprints (from a classic board) will not appear on the next-gen board. Any issues allocated to a shared classic sprint will appear in the next-gen backlog.

Next-gen kanban boards are not compatible with shared sprints. Currently, we’re unable to support next-gen kanban boards when using global sprints as this is not supported by Jira.

Increment Roadmap

• Classic or next-gen issues can be scheduled into any of the teams swimlanes. This is because because you’ve specified the issue link type that links classic and next-gen issues to the Roadmap issue

Team Planning Board

• Issues scheduled into a next-gen and shared team swimlanes will be shown on the next-gen team planning board

• Next-gen issues will be shown on the backlog and can be scheduled into the increment sprints

• Dependencies can be created and viewed between next-gen and classic issues

• Click on a roadmap issue to show the linked issues

• Click on a roadmap issue and use quick create to link a new issue