Next-gen Tasks not showing up in custom Classic board filter

[Deleted user]

Hello all,

Context

I have a team that is trying to take baby steps away from their Next-gen board since they are happy with it for most purposes, but need better visibility into other team's issues that sometimes get assigned to their team. Because of this, they have a requirement for a Classic board that aggregates their work all in one place.

Problem

I made a Classic board in another project they access that aggregates many projects, but Next-gen Tasks won't show in the Backlog. Stories and epics are showing up, but not tasks. It is also noteworthy that these tasks show up in the board's Active Sprint view along with all other issues and only fail to be exposed in the Backlog.

Example classic board query

project in (CLASSIC1, CLASSIC2, NEXTGEN1) order by rank

Backlog shows

- All CLASSIC1 Stories, Tasks, Bugs

- All CLASSIC2 Stories, Tasks, Bugs

- NEXTGEN1 Stories, Bugs, Epics not Tasks

Active sprint view shows

- All CLASSIC1 Stories, Tasks, Bugs

- All CLASSIC2 Stories, Tasks, Bugs

- All NEXTGEN1 Stories, Tasks, Bugs

Could this be a bug?

Thanks in advance for your help!

[Petter Gonçalves · Accepted solution]

Hello @[deleted]

Thank you for reaching out.

Per your description, it seems that your Next-gen issues are not displaying in the backlog of your Classic board. Is that correct?

Can you confirm if you are using a Kanban or Scrum board? Since Next-gen boards use unique entities (Including Status), please make sure you have properly mapped them to the backlog column under ... > Board settings > Column.

Additional to that, are the Next-gen issues returned when you run the board filter?

Also, It is possible that you might be facing the bug below:

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

Let us know if you have any questions about this.

[Deleted user]

Hi @Petter Gonçalves ,

It is precisely the bug you've linked. Thank you for clarifying there is no resolution to this at this time.

Best,

Stephen

[Petter Gonçalves]

You are welcome, @[deleted]

Have a nice day.

[Karo Sarkisyan]

+1

Next-gen issues are not displaying on the board of the Classic project.

Is there any reported issue?

[Emily Chan]

Hello @[deleted] ! We’d like to learn more about your context and your use cases. Would you be willing to have a one-hour chat with us? It would be immensely helpful with understanding about organisations that are using both Classic and Next-Gen projects, and we’ll also send you a $100 gift card in appreciation for your time. If you’re willing, please email me at echan@atlassian.com