Multipe boards and board filters in next-gen Scrum project?

[Rondo Lehner]

Currently we are using a single classic scrum project with multiple boards that pulls in issues from multiple other classic scrum projects via board filters.

While exploring the next-gen scrum projects I didn't see the option for board filters or multiple boards in a project.

• Do next-gen Scrum projects support board filters?
• Do next-gen Scrum projects support multiple boards?

Thank you

[Alexey Matveev · Accepted solution]

Hello,

I also can not create multiple boards for an next-gen project. I guess, it is not possible.

[Miranda Casey]

I'm having the same issue. It seems as though the process followed to create a new board on a Scrum project is not available for next-gen projects. Honestly, that's a huge bummer because we utilize multiple boards for our projects, and if the next-gen projects do not allow this then it's not going to be utilized at all. 

[Adrian Dent]

Yes, same here. I have multiple projects running and want a single view across all to show the work being completed for that Sprint by various teams. A Scrum of Scrums board would so helpful. I'm now looking to "hack" something possibly using filters, tags and labels... so far that's not working either. One board to rule them all... 

[Chris Pearce]

A +1 here for having multiple boards in projects. Hugely important feature for us.

[cmorreale]

Same here... I am used to setting up a main project Scrum board, and multiple Kanban boards as part of a project.  Is this not possible with next gen?

[Arba]

Same here..
I use single scrum board with filter to All Project.
That's work great to manage all Scrum and Kanban Type Project.

However, i found that we seems unable to add Next-Gen Project into the Scrum Board.

1. In Backlog Page, epic is a group of issue that classified issue in the tab. But for Next-Gen Project, Epic/Roadmap is considered as issue there.

2. Any issue type from next-gen project (task, story, etc.) cannot be added into sprint. First i think i success to drag the issue from backlog into sprint, but if i refresh the page, the issue back to backlog again.

[Ilgıt Yıldırım]

+1.

I'd also love to have this feature. It is important to have a cross-board view from multiple projects.

It is likely quite a lot of people juggling more than one project at a time.

I hope to see this feature added for next-gen projects soon too.

[Prakrati Saxena]

+1. I need to create a common dashboard with the status of multiple next gen projects for high level update. I have created a query which gives me list of issues across projects but when I add a two dimensional filet to dashboard and select the custom field it breaks. Apparently custom fields are linked to specific project and only one can be selected at a time. It's wired , please add this to next gen. It's really required.

[Adrian Dent]

I found a workaround for me which works quite well.

I set up a dummy project in JIRA Software in CLASSIC mode (SPRINT of SPRINTS) with a limited number of stories or epics. Maybe one EPIC per sprint for instance titled "JAN-SPRINT1".  Then I add the Story/EPIC to a Sprint and rename the Sprint to JAN-SPRINT1 as well. Using the CLONE option I set up several more EPICS and rename them so I can create sprints up to the end of the quarter. FEB-SPRINT1,2, MAR-SPRINT1,2,3 (base on two weeks each) etc It doesn't take long.

Next I go to each active project and assign each ticket to a relevant sprint, for instance, JAN-SPRINT1. 

Then I create a New Dashboard and select "add a New Gadget", followed by Load All Gadgets. Scroll down to the "Filter Results" gadget and add it to your Dashboard, fill in the details to show the results and the required filter (JAN-SPRINT1), and set it to refresh every 15 minutes. I set up the following fields to display in the gadget.

• Sprint
• Key
• Summary
• Story Points
• Assignee
• Due date
• Status

I create a second gadget for JAN-SPRINT2 (to represent to the months second and future sprint). I don't do a backlog view for all tickets, mainly because the list would be so great and because you can get this list from a regular filter (all open tickets).

However, when we do a sprint grooming session for each project we can then associate tickets for consideration in the next sprint by assigning them to JAN-SPRINT2. 

The only downside, I need to refresh the gadgets on the dashboard at the end of each sprint to filter for the next SPRINT backlog and CLOSE the current sprint. I also need to update the original SPRINT of SPRINTS to close a sprint and start a new one. (None of this takes a lot of time - and saves me more pain and stress).

I can monitor progress regularly, and present to senior management easily too. I can show who's working on the ticket it's status. 

Each project will also group their tickets by the active sprint and future sprints you assign to the tickets. 

You can do this if you have JIRA Software (Cloud) as don't get the option to created sprints in JIRA Core (Cloud).