Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Next-gen issues on traditional board

I've got a multi-project kanban board set up and we've been using it for quite some time... Generally, it pulls issues from our projects and shows each in-flight epic as its own swimlane and the columns show the state of the storys/bugs that are associated with the epic. 

I recently started setting up a next-gen project and wanted to pull it onto this board. I have updated the board filter to pull in the epic/stories from that board and my initial test story is showing in the saved filter results. I didn't initially, but I now have also updated the columns to ensure the next-gen statuses are mapped appropriately (and the count even reflects what I expect to see), but when I view the board, the issue is not showing. Is there a limitation that prevents next gen issues from showing on the board? All signs suggest things are in order, but when I view, nothing...


Screen Shot 2019-12-23 at 9.28.37 AM.png



1 answer

1 accepted

2 votes
Answer accepted
Jorden Van Bogaert
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 23, 2019

Hi @Brad Barton 

I think Next Gen issues don't use the 'fix version' that default Kanban boards use in their subfilters. So if you removed the Kanban board Sub-filter (all the way at the bottom on the board configuration), you'll see your next gen issues show up.

Kind regards

Like Jorden Van Bogaert likes this

Great solution! Addresses this issue as well:

Like Jorden Van Bogaert likes this

Sounds great; However, it doesn't seem to work for me, at least.

We have this specifically in the sub-filter for our Classic Kanban board's Settings → General configuration:

fixVersion in unreleasedVersions() OR fixVersion is EMPTY 

If I remove that entirely, and make sure that the filter used for that Classic Kanban board does cover issues from the Next-Gen project,  I still do not see these Next-Gen issues show up on our Classic board.

(Also, as pointed out elsewhere, it seems with this solution, the Backlog board still would not contain Next-Gen issues, FYI.)

Like # people like this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events