Issues lost during migration from Classic Project to NextGen Project

[Liz Truong]

Hi, 

I migrated issues and tasks from a Classic Business Project to a NextGen Project. It looks like many of my tasks/issues did not migrate over. I started with 83 issues and now on the new board, I have 38. Where did the issues/tasks go?

[John Funk]

Hi Liz,

I would start by just running a query for the project to see how many issues actually show up. Something as simple as:

Project = ABC

If all 83 issues show up, I suspect it is a problem with the filter used by the board and Trudy says. Maybe there is a sub-filter on the board even. 

[Liz Truong]

@John Funk 

how do i run a quaery for the project? right now, because of issues that I added, I see a total of 67 issues.

[John Funk]

See my example above for syntax.

To start, click in the Search box

Then click on Advanced search for issues.

Then put in the search.

[Liz Truong]

@John Funk that was helpful, I now see a total of 136 issues for the board. How can I remove the filters on the board?

[John Funk]

Go to Board settings > General 

There you can see the filter that is attached to the board and change it or connect to a new one

[Liz Truong]

@John Funk How do I find the Board settings? I see the project settings and Atlassian account settings, but no Board settings. 

[John Funk]

While on the board, click on the 3 dots menu on the right and select Board settings

[Trudy Claspill]

@John Funk 

I'm not the originator of this post, but commented on it early on.

I haven't worked with NextGen projects before, so I set one up for myself with the Kanban template.

The ellipses button on the board lists only "Manage Rules". There doesn't seem to be a "Board Settings" option like we see on boards for Classic projects.

[Trudy Claspill]

@Liz Truong 

Since I've now set up a NextGen project with the Kanban template, here's what I noticed.

1. The only issue types available in the Create Issue dialog were Epic and Task

2. I could add a "child" issue to the Task issue.  It got assigned the Subtask issue type and it does not show up independently on my board. Instead a little icon has been added to the first issue to indicate it has child issues.

3. I created an Epic type issue. Epic issues also don't show up on the board as cards, but a Quick Filter was added specifically for displaying the child issues associated with a selected epic.

So, in migrating your issues from your other project, did you migrate Epics and Subtasks? If so, perhaps those are the "cards" that are missing from you board. I don't see a way to force those to display on the Kanban board of a NextGen project, but I've only spent about 15 minutes looking at this.

Hope that helps.

[John Funk]

@Trudy Claspill  - Ah, I forgot this was Next-gen - nice catch!!

[Liz Truong]

@John Funk Trudy is right

[Liz Truong]

@Trudy Claspill I migrated Tasks from the Classic Board, and I do not believe there were Subtasks on the old board, but I could be wrong. When I created my NextGen project, prior to the migration, I created a Subtask issue type, so Subtasks should have migrated, in addition to any Epics and Tasks. 

[Liz Truong]

@John Funk @Trudy Claspill I really feel I need to discuss with JIRA customer support at this point. How do I do that?

[Trudy Claspill]

@Liz Truong 

Go to this URL to open a ticket: https://support.atlassian.com/contact/#/

Post the outcome, since what you learn might help others. :)

[Liz Truong]

@Trudy Claspill where can i submit a ticket on your link? when i go through the prompts, it directs me back to posting something on the Atlassian Community board.

[Trudy Claspill]

@Liz Truong 

When I use that link it redirects me to the first step of entering a support ticket, or to logging in with my Atlassian Cloud account if I'm not already logged into JIRA.

How is it redirecting you to post to the Community?

[John Funk]

Hi Liz - It sounds like you might have a free account which does not provide support. 

Another thought - you said your query turned up 136 issues for the board at the time. How many of those were Done? It might be that some dropped off the board. 

[Trudy Claspill]

Hello Liz,

Welcome to the community.

When you created your nextgen project, which template did you choose - Kanban or Scrum? 

Did you use the Bulk Change feature to move the issues from the classic project to the nextgen project?

Could it be the filter set up for the board is hiding some issues?

I notice there are some caveats about migration listed in this document. Could any of these be affecting you?

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/

[Liz Truong]

@Trudy Claspill 

Thanks for the reply.

1. My nextgen project is Kanban and my old project was Kanban too.

2. I used the Bulk Change feature.

3. I do not see any filters or rules for my boards. Let me know if I am missing the filter button here.

4. I checked all of the caveats and I do not believe there were active sprints, components, versions, or releases on the old board, especially since it was a business project Kanban.

Let me know your thoughts.