nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create multiple Next-Gen boards

Abhijith Jayakumar

We have created a new project using the new Jira and it comes ready with a next-gen board. In our project, we were hoping to manage 5 different types/modules of activities. We were hoping to utilize 5 different boards to track each of these types/modules. While this was possible on the old JIRA with traditional Scrum/Kanban boards, I am unable to create an additional Next-Gen board.

I checked my access and I seem to have the access to create a board and am able to do with all projects in the older version of Jira. Could you please advise

Accepted answers

Eoin

Please add your votes to https://jira.atlassian.com/browse/JSWCLOUD-17371 and watch the suggestion to get automatic updates.

We will be bringing multiple boards to next-gen projects, although we have yet to start this work.

Thanks

Eoin

Product Manager

All comments

david_fsrxhm

Hi @Abhijith Jayakumar the next-gen projects are standalone board based. They are designed to be like that

Abhijith Jayakumar

Thanks @david for the quick response. Considering this behavior, what would you recommend utilizing to manage/represent different modules, streams within a project.

david_fsrxhm

I would recommend to separate them into different Issue Types so you can filter easily by them in case that they behave differently.

You can also use custom fields that will apply to issues and allow you to set specific information for them.

Philipp Herzig_e3h1fg

Another workaround would be to just create 5 next-gen projects. This won't take more time than creating 5 boards based on different filters in classic projects.

Jared Krause

👋 I'll chime in as well. We would also love to use multiple boards.

One board for active design + development.
One board for ideation + requests + parking lot.
These boards are too different to rely on filtering issues. You're forcing people to add 10+ columns on one board.
Multiple projects isn't ideal because we want a shared roadmap.
Currently, we're using the Backlog as our ideas + requests and the Board as the design + development section. This isn't necessarily how it should work, and doesn't allow us to utilize the Sprint feature.

Thanks for listening.

Jared Krause

I'd also like to delete a post after I accidentally post an answer instead of comment, haha

Justin Couto

The way we doing this is by creating different labels and then filtering our board by them. This should enable you to have things like a UX label, a Development label, or a module label like "Account Management"

DENISE M WATSON

Please add the ability to have multiple boards for a project. I thought when I moved over to NextGen I would finally be able to track work by creating tasks on a board rather than having to remember to label everything carefully to ensure the boards only displayed what we needed in JIRA classic - now I have no additional boards and still have to carefully label to get tasks to display together. I want to get away from labeling dependency to categorize work. It creates an opportunity for mistakes.

Gonza_cbo4gg

The roadmap feature is awesome, but only make sense with multiple boards, it is counterproductive and not very user friendly if we need to create multiple projects that will never interact with each other unless we bulk edit to migrate tickets between them

Iris Blankenship

Hi, we are also very unhappy with the fact, that we are not able to create a scrum and a kanban board within one project. Any updates from atlassian on that?

Nina Shulyak

PLEASE allow JIRA next gen to have multiple boards for one project, ideally with the workflow:
1) board for PRODUCT manager to work on ideas, refine them, move further
2) board for DESIGN, ideally would be triggered by a workflow: once task has "ready for design" status, it would jump into "todo" on designer's board
3) board for each platform - to see clearly the progress on tasks
4) board for QA team: once dev sets status "ready for QA" it will automatically fall into "todo" on QA board
5) if QA verification fails, task should be back to developer in REDO status with a higher than "todo" priority

simplified flow you could see here, i visualized on the diagram (of course, there are open question to answer and there are many things to refine with multiple environments, but you get the basic idea)
multiple boards example.jpg

Laurent DuBerger

Yes! +1 here

Cesar Salazar

Nice diagram! If someone suggest a tool where I can implement this flow and has the simplicity of JIRA next gen I would switch immediately

Edmund Reed

Hello, I'm wondering why no official response has been given despite the very obvious need for this feature from customers/users?

Ieva Langenfelde

The same problem here!!! Also looking forward to seeing the official response to this. Already ~1year ago in Confluence conference I talked to Jira representative and didn't get any good suggestion on how to manage interactions in JIRA among ios,android,backend,qa,po etc teams. I was left with the impression that they feel that is some kind of an edge case, not a normal mobile development team setup. (Like - really?) But now with the next gen project there is even no possibility to do multiple boards. Wtf seriously? In which ideal world it will be enough to use just one project with one board? If it is meant for small teams, then those small teams most probably will stick to Trello, not going to Jira at all.

I just don't want to deal with extra work by making lots of different projects or making fake tags or custom fields. I want JIRA to work for me, not that I am working for JIRA.

Fernando Nuñez_5q1g9f

Looking forward for the official answer!

Rich Hardt

We too would love to have the ability to combine several Next Gen projects into one board. We have a small team of developers that work across various projects. Using a combined board, we'd like to see if we are overloading our developers.

Jelle Pals

We also like this feature

Tomáš Sezima

+1. Multiple project boards would make the experience better for both developers and management.

Syed Rahman_bifqjk

why remove such a great feature of multiple boards- disappointed with the lack of response or reaction from Atlassian

Edmond Melkomian_d8mrp1

We solved this problem, by creating multiple columns. We created a column waiting tasks, so we can move them there.

Joe Sandmeyer

Props for finding a workaround that you like. Hopefully this lack of multiple boards problem will be fixed so we can avoid workarounds.

Vijayan Poongavanam

Hi, Any idea when they are going to implement this multiple boards creation for Next-Gen projects?

Eric Keyte

We desperately need multiple boards.

Joe Sandmeyer

If desperate, try one of the workarounds described above

Jelle Pals

The only solution is using the old version :P

Edwin Ng_wwj8ny

Nice diagram.

In order for this to scale well, I think what is requested for here is for an overarching Next-Gen Roadmap that can link across multiple project stories which the separate devs teams can chunk to their respective tasks and subtasks rather than a single project without overwhelming the Product Manager with too much detail.

Hans Son

we need multiple boards for next gen - or at least custom filters on next gen - this is a deal breaker!

Jamie McCollum

We definitely need multiple boards, and we can't use next gen projects without it. I also haven't found any workaround to allow the previous functionality where a single board could include issues from multiple projects.

Matthew Patulski

+1 for Multiple boards on Next Gen.

Hanna Åstrand

+ 1 for multiple boards!

Luis Locon

+1 for Multiple boards on Next Gen.

Joe Sandmeyer

I wholeheartedly agree with the need for multiple boards in Next Gen projects. While imperfect, did you try any of the workarounds mentioned above such as creating multiple boards in a Jira classic project if only to use them in Next Gen projects?

Florian BRUNIAUX

+1 !

Stefan_Ojanen

+1, just testing this out to have the Roadmap feature but this is useless without multiple boards

Jackie.Keys

Hi @Joe Sandmeyer

I am new and missing the point on how the classic boards are working in the next gen projects - the next gen PBL does not show in the classic boards...

Would you mind please elaborating on how this workaround works?

Thanks very much

Joe Sandmeyer

Hi @Jackie,

To demonstrate, start by creating a search that includes all open tickets for two different projects. One project can be classic and the other next-gen. You can try saving this as a filter. If you get this far you are halfway there.

Next create a new board in a classic project and go into the board settings. Set a main filter for this board that is like the filter you created in the previous step. This will prove that you can create boards in a classic project that include tickets from other projects including next gen.

Go on to set up columns and swim lanes as you would in any board.

I hope this helps.

-- Joe

Valentina Ical

Multiple boards please in next gen please!

alvaro1

emily.daye

Multiple boards would be super helpful for next gen! please

gsigety

multi boards for next gen project guys !!!

unknown

+1 for multiple boards

We have a small team, so a decent workaround for us is that we I have categorized each focus area into a seperate epic, and then grouping by epic on the board view (using "group by" drop-down).

For example, there's an epic for Support, and so our dedicated support guy just collapses the other epics on the board, and works like that. Then, if he's adding an issue, it's automatically added under the Support epic.

In terms of your request for a parking lot and ideation, the roadmap is a nice place to manage that, just add future issues on that view - then anything on the board is active development or support.

I hear what you're saying about having different statuses for different kinds of work... not sure how to handle that in NextGen.

Fred Gayton

@Nina Shulyak That is an amazing diagram. Would you be able to share what tool you used to create it? I really love the clean simplicity and the sticky notes.

Drew McManus

Years later and this is still not a feature. #JiraFail

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

agile

board

next-gen