Migrated JIRas from classic to next-gen not appearing on backlog/board

[Rakesh Goel]

Hi,

I migrated all the tickets (JIRAs) from classic to next-gen project,

It is showing the epics in roadmap. But none of the tickets appear on backlog or board.

Pl. help.

[Candace Holcombe-Volke]

I know this is late, but stumbled on it today so hope it helps someone in the future. 

Make sure your board is configured so that the last column is the "Done" column. If you have anything else as the far right column, Jira will consider it done and pull it off your backlog. I migrated some classic tickets, which showed up briefly, then disappeared. I recreated them directly, and the same issue.  Was scratching my head on this for 20 minutes until it finally dawned on me... 

[Duke Coulbanis]

I have the same problem with the original author with a slight difference. My WIP items (which were on the previous board) all appeared but were added to the backlog. I then moved them into the board section and they are properly there.

However, the items that were in the backlog on my classic kanban project do not appear in my next gen kanban project.

I activated the issue viewer feature on the next gen project, and all 48 issues are listed there...

The board has the 27 which were on the classic board... but the 21 issues that were in the backlog do not appear in Backlog or Kanban board... Only in Issue Viewer.

Here are my responses to the questions you asked @Petter Gonçalves :

1) Yes, some of the issues migrated were/are sub-tasks... I made sure that there was a 1-to-1 mapping for each of the Issue Types from my classing project to my next gen project, and they were all migrated accordingly.

2) Yes... the JQL filter returns 48 issues, but the issues are all also visible in the Issue Viewer which I have turned on when I created the Next Gen project.

3) To my knowledge, yes... As with 1 I made sure that all the columns that existed in my classic project had a counterpart in the next gen project, and in the migration wizard I selected the appropriate mappings in step 3 of 4.

4) Yes, the backlog feature was turned on prior to migration from classic to next gen.

5) Both classic (source) and next gen (target) were Kanban projects.

Thank you, in advance, for any assistance you can provide.

Best regards,

Duke.

[Petter Gonçalves]

Hello Rakesh,

Welcome to Atlassian community!

There are some possibilities that can be causing this problem. Please, check the following topics and let us know what you got:

1 - Are the issues you migrated sub-tasks? Next-gen projects do not support sub-tasks, so any issue which is not configured with a Standard issue-type will be lost as mentioned in the documentation below:

Migrate between next-gen and classic projects

2 - If you search for the Next-gen project in the Issue navigator (JQL filter), did it return the mentioned issues? 

3 - When you moved the issues to Next-gen, what statuses you selected for them? Are they properly mapped in your Next-gen Board as a column?

4 - Is the backlog properly turned on in your Next-gen board (Project settings > features)?

5 - What are the templates of both projects (Scrum or Kanban)?