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; } } }

Any way to include next-gen issues in a classic board ?

Ian Bussières_ba3y9n

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 ?

Accepted answers

Petter Gonçalves

Hello Ian,

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.

All comments

Petter Gonçalves

Hello Ian,

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

Let me know if it works for you.

Ian Bussières_ba3y9n

That works, yes ! Thanks.

Have to admit that the multiplication of identical statuses is a bit of an annoyance, but I think we can live with it for now.

Andrew Lee

@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.

unknown

@Petter Gonçalves same trouble as @Andrew_Lee ; I edit the filter in order to retrieve issues from a next-gen project; I get those issues in the "Board Settings > Column management Issue count preview" but no issues (from that project) displayed in the Board;

this is very frustrating, can you help?

Petter Gonçalves

Hello Everybody,

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:

- Issues from a Next-Gen project which are part of an Epic do not appear in a classic backlog when included in the filter for a classic board

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.

Rob Wilson_7d7sj5

That looks like the one. All my issues are linked to Epic, they all appear in the Board setup page for a Classic board, but never appear on the actual board.

Hope we can see this fixed soon. It's pretty much a shower stopper for us to start using these Next Gen projects.

Andrew Lee

@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!

Peter Gleeson

@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:

Screenshot 2020-01-21 at 11.08.05.png

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.

Mark Crocker

The above works but we cannot control the rank due to the way epics are not epic links here.
Anyone have any smart solutions?

Julia @ 55 Degrees

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.

Screen Shot 2020-02-11 at 7.06.29 AM.png

So, if you haven't already, try removing the kanban board sub-filter and see if that works for you!

Julia @ 55 Degrees

(nothing to see here, updated answer)

Manuel Venegas_dqw1g9

This works like a charm! thanks for that

Mark Crocker

Awesome. This works. But how we do now release issues to clear the done column?

Jean-Nicolas DESJARDINS_luh8jq

Here we got issues from classic and next-gen on a classic board, but we got an issue on the Story Point ans Estimate Story Point. The classic board can't display the value in active sprint and backlog.

So Po's work is pretty hard to adapt sprint to the velocity of the team. Is there any solutions for solve this issue ? We can't migrate classic to next-gen or reverse at the moment.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

next-gen