I just ran into an interesting issue with next-gen boards on Jira cloud.
For our company we need different product backlogs, aggregated on to one board for a team to work on.
We have set up our different products into next gen projects. Each of them has their own backlog. Since we don't have a team per product yet, we created an aggregated classic board, which uses a filter to select tickets from different products/projects.
When looking at the results of the filter I see all of the required tickets, but when I then go to the board that uses this filter all of the tickets that have an Epic as parent are gone.
When using the same workflow with 2 classic boards this issue does not exist. Is there a way around this?
