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
Hi everyone! Like Abhijith, I wanted to use a next-gen project (because I really like the roadmap feature) but I need boards for multiple teams (Discovery, Delivery, Services, etc.) with their own workflow. I would like to roll all their tickets up into a central set of Epics. Two questions:
1) Any suggestions about how best to accomplish this?
2) Does anyone know if JIRA will add the "Roadmap" feature to their classic Scrum and Kanban projects soon?
We have multiple projects for either different systems or teams and previously we could run a single sprint from a single board, but now from what I can tell there is no way for a single project board to filter other projects into its scope. So the "work around" is to run multiple sprints across all of the projects?! :/
I'm not sure I really consider that a workaround. The other alternative I see presented here is to scope each systems stories and all teams involved into a single project and try to separate their concerns via custom issue types/fields? Yikes!
Sounds like the short answer is there is no answer.
My team needed to use roadmaps, and they were only available in the next-gen template, but I also wanted to use multiple boards for my team. This created quite a dilemma for us. I ended up creating a separate project instead of a board, but it would've been ideal to create additional boards. Oh well.
Just chiming in to say I'd like multiple boards in a JIRA next-gen project too.
Getting real tiresome waiting for JIRA next-gen to catch up to the same features as before. The mentality of take everything away and see what the community wants to put back in is kinda annoying.
Create a jira classic project. Create as many boards as you want even if only using them for next-gen projects.
I agree with other posters here that there is no good reason to avoid offering multiple boards in next-gen projects. I assume it is only because they have not gotten around to implementing this yet. Until then, I'm using this workaround.
1. Have an existing SRE team using backlog made up of tickets from different projects
2. Want to use roadmap to bring structure to our kanbans so make Next Gen project
3. Can't work out how to get backlog to show existing issues for team
4. Discover its not possible and Atlassian don't appear to give anything more than 'Nope, not supported yet'
5. Dump next-gen and make classic project to incorporate team members
6. Discover that 'next gen' uses its own status values so our boards will become outdated when people on other teams change their status codes
I remember when Jira actually worked.
How I see it now. Nex-Gen projects do not fit any of the very minimal needs of my work. We use multiple boards, for different issuetypes, with different columns, with custom colors, different swim lanes, etc. Some of the boards share the same issues, just present a different view , different columns, for a different audience. Some boards actually blend issues from different projects, and I could continue here with more missing features ....
In summary, it seems a giant step back, and probably it will pass some time before we even consider using the next-gen projects. BTW, the roadmap feature was attractive only if it could show multi project views, like a portfolio or program. So, no worth in doing any workaround to get the roadmap feature to work for now.
👋 I'll chime in as well. We would also love to use multiple boards.
Thanks for listening.
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.
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.
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)
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.
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.
My team has been wanting to transition to next gen for about a year. We hesitated for a while because there was no "fix version" option in next gen. Now that there is a solution for that, we were about to transition, but i've just realized that next gen doesn't allow for multiple boards. Apparently this is intentional? as designed?
This is a hard blocker for us preventing us from making the move. We are a mobile app developers. We have multiple epics and features that require work from multiple teams - art, client engineers, server engineers, but not all of those teams have the same work flow or process for testing and deploying work. In Jira classic, we utilize multiple boards on the same project that we can feed tickets from the same epics into different board views and flows that are appropriate for each team.
I've seen a suggestion high up in this thread to just just filters on the board. That solution doesn't help us, because problem isn't what tickets we do or don't want to see - its the columns. My server team wants to see different columns from my server team. We want different boards to respect different status and flows.
Next gen looks so great and I love some of the tools they offer- however, things like this, and the earlier lack of fix versions, really confuse me. Who is next gen designed for? What is the use case and who is your ideal user? It doesn't appear to be teams like mine, unless i'm missing something. This is a genuine question and I would love to know if i'm not thinking about board management in the correct way.
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.
Sorry to bug you again. I have been testing this with dummy data in dummy projects
1. The statuses are mapped for each column and there are no unmapped statuses in the classic project
2. The query in the search shows all the issues I expect
However, when I apply the query in the Classic project board filter, the issues as per above are not showing.
Is there anything else obvious that I am missing please?
Thanks very much :)
Hey Next-gen fans, Would you like the opportunity to give direct feedback to the Next-gen product team? Would you like the chance to preview and test new Next-gen features? I’m excited to annou...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events