We have been using a multi-project filter to feed our classic jira board. This is useful to get an overview of all projects and team reports for all projects brought together. We are a small team with multiple customers we serve every sprint, so this was useful to us.
We love most things about next-gen board, but we have not yet found a way to include issues from next-gen inside a classic jira board. Is this even possible ?
If you edit your board filter to return issues from a Next-gen project and map the statuses in your board column, it should properly display the Next-gen issues in your board.
The specific steps would be:
- Navigate to your classic board > Click on the three dots Icon > Board settings > Edit filter query
- Add your Next-gen issues to be returned in the board filter
- Back to your board > Project Settings > Columns
- Add the statuses of your next-gen issues to the columns of your board
P.S: Next-gen issues have its own set of statuses which can have the same name as your Classic Statuses, so don't get surprised if two In progress statuses appears to be mapped in your board columns.
Let me know if it works for you.
@Petter_Gonçalves, I followed your instructions above and can see my next-gen issue status (and associated count of them) under Project Settings > Column, however when I go to the Board it only renders the issues from the Classic board - it does not render any of the issues from the Next-gen projects.
Are there any other restrictions that I need to know about? The issues that I have are a custom issue type in the Next-gen project.
Hello @[deleted] and @Andrew_Lee
Please, check the following:
1 - Make sure your board filter/sub-filter does not have any parameter that might be removing the issues from Next-gen, like "resolution is empty". In fact, perform a search with the board filter and check if it returns the next-gen issues.
2 - Check if any quick filters are being applied to the board
3 - Check if any swimlanes are applied to the board. If there is, remove them and check if the next-gen issues appear.
Hi @Petter_Gonçalves ,
and thanks for your reply; still experiencing the issue; check as follows:
@[deleted] I see you have an unmapped "Backlog" issue status in your screenshot (item #6 of your checklist). Not 100% sure of what I'm saying here, since it also says there are 0 issues. But did you try mapping it to a column, so I think you want to drag that status to the "Backlog" column along with the other "Backlog" issues status.
I have a client that was experiencing the same issue as the previous posters (the one not resolved by other workarounds).This is what just helped her resolve the issue:
in Board settings, at the very bottom, the Kanban board sub-filter needs to be removed if you have not enabled versions.
So, if you haven't already, try removing the kanban board sub-filter and see if that works for you!
@Gui and @Julia___55_Degrees and @[deleted]
Have you guys managed to rank these on a board at all?
I can't get it to work and have read other forums and threads about why it doesn't work:
I'm curious as to whether there is a workaround
Wondering if someone has/had the same problem as I have now.
After enabling the version in the Next Gen, I am able to see the issues. I have this scrum board where I added all the status in the respective columns from the different projects. When I do the main filter in the board, I can see all issues, so thats good.
But when I go to the Backlog of the scrum board, if the Next Gen issues do not have an Epic assign, I can work normally with those tasks, but when the Next Gen issue has an epic assign... well I can just see all the Epics in the Backlog, not the tasks under them.
I am able to rank, but not see the tasks under the epics. I tried removing the ranking, but same thing. I see the tasks for all projects, but in the case of Next Gen with Epics, I can see just the Epics.
Appreciate the help if someone has input.
Thank you for your patience while we investigate this issue.
After some time testing and trying to reproduce your scenarios, I noticed that you might be facing the following bug in Next-gen:
Basically, next-gen issues that are linked to an epic in next-gen projects do not appear in Classic boards, even if the board filter is clearly configured to return it. Could you guys please confirm if that's the case?
If it is, we recommend you to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.
About @Peter Gleeson comment:
Same issue here. Very frustrating, and a waste of time trying to figure out.
Atlassian's handling of next-gen Jira projects are a masterclass in how not to roll out a product upgrade.
We are sorry to hear you are not satisfied with the new Next-gen template, Peter. In fact, Next-gen is not a product upgrade, but a new/different option for those users who felt overwhelmed by the complexity of JIRA Classic template and requested a simpler option, straight to the point with fewer options of customization.
We hope our next upgrades in Next-gen can provide you with the features you need.
Let us know if you have any questions.
@Petter_Gonçalves, I was that bug report and thought that was the cause but when I checked my Next-Gen project, it had no epics configured so I do think it's a larger issue than just tickets associated with Epics. Be interested to see if others also have the issue with issues not linked to an Epic or if it's just me!
@Petter_Gonçalves Thanks for the swift reply.
next-gen issues that are linked to an epic in next-gen projects do not appear in Classic boards, even if the board filter is clearly configured to return it. Could you guys please confirm if that's the case?
This is not the problem. I've also created issues not linked to Epics that still do not show in the Classic board.
The bizarre thing is, the JQL query for the Classic board returns each of the Next-gen boards under "Projects in board".
It also counts the number of issues when mapping columns:
So, it appears the Classic board can "see" the issues from the Next-gen boards. Yet, it will not display them.
It's concerning a bug like this could make it to production. Did no one properly test compatibility between Next-gen and Classic?
Can you confirm when this issue might be resolved?
For now, I've advised my team to move back to Classic projects - even though these are over-complex and notoriously bad from a UX point of view.
Thank you very much for all the feedback provided about this thread.
After some time investigating it further with our developers, we noticed another bug that can eventually happen when configuring next-gen Kanban issues in Classic Scrum boards:
The bug above does not happen for every single Cloud instance, so that was the difficulty we had to replicate and properly diagnose it as a bug (Although the bug was created in October 2019, it took more time to confirm the proper steps to reproduce it).
Please, try the workaround below and check if the problem happens again:
We are having this issue as well. The workaround does not work for us either.
Problem: Classic board not able to display issues from a next gen project. In the classic board column setting, I see the statuses with the number of issues listed, so the filter appears to be working, but when we view the board, no issues from the next gen board are displayed.
I spent hours configuring a next-gen project and then almost another hour to figure out why it doesn't interoperate with the classic projects. Sorry to be so frank, but why isn't this issue being addressed with High priority?
According to https://jira.atlassian.com/browse/JSWCLOUD-17987 it is of Medium priority without an owner. However, if old and new projects cannot live side-by-side we'd either have to migrate all to Next Gen in one go or not use Next Gen at all.
Maybe if they had called it something like "Simplified Projects" instead of "NextGen", people would be less confused. Oh well.
I for one like the NextGen as it does meet some needs for Jira users outside of Software Development, but I hope that some of the field mapping between it and classic projects get a bit tighter so the boards and filters treat them the same.
In fact, Next-gen is not a product upgrade, but a new/different option for those users who felt overwhelmed by the complexity of JIRA Classic template and requested a simpler option, straight to the point with fewer options of customization.
But then how do you explain releasing features that are only supported with Next-Gen projects, such as the Roadmap? Jira Classic certainly seems to be a product heading towards end-of-life, as evidenced by the long backlog of bugs and feature requests that go unfulfilled, while you focus on the new Next-Gen product.
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