What happened to the tickets I migrated from one project to another?

[Hilary Bond]

I attempted to migrate tickets from one project to another. I retained all fields, and selected migrate child tasks. Now they don't appear in the original project or in the new project. Where might they have gone? 

[John Funk]

Hi Hilary - Welcome to the Atlassian Community!

If you are trying to see them on the existing board, no they won't be there. If you create a filter and use something simple like: project = ABC where ABC is the project you migrated the issues to, you should see them there. 

[Hilary Bond]

I am looking for them on the new project but they aren't there. I also don't see them in my recently viewed or updated tasks in all issues view. 

[John Funk]

Can you provide the exact query that you used to search? 

[Trudy Claspill]

Hello @Hilary Bond 

Welcome to the Atlassian community.

If you have one of the original issue keys, you can type that into an issue search and it will automatically redirect you to the issue under its current issue key.

Use of the Move Issue function does not generate an entry in the system Audit Log, so the automatic redirection or otherwise searching for the issue by other data in other fields will be the methods you can use to find the issue.

[Hilary Bond]

Unfortunately, I don't have the issue keys... it was >150 issues. I do know the parent they were under on the original project and have tried searching for tasks that were associated with that parent, but they aren't showing up. 

[Trudy Claspill]

What type of project is the source project?

What type of project is the destination project?

Get that information from the Type column on the View All Projects page under the Projects menu.

When you say you "migrated" the issues, do you mean that you used the Move Issue function? Did you do that through the Bulk Change feature?

How did you generate the list of issues to move? What was the filter that you used?

What type of issues were moved? Were they subtasks? Standard level issues? Epics?

Have you confirmed that you have permission to see the content of the destination project?

Does the destination project use Issue Security? It is possible that Automation Rules set Issue Security for the issues as they were moved into the project, and you don't have permission to see them anymore.

Moving an issue will change its Updated timestamp. You could try executing a search to look for any issue where the Updated timestamp is newer than a date/time in the past prior to when you executed the move. You can augment the search criteria using the criteria that you used to get the original list of issues that you moved.

[Hilary Bond]

What type of project is the source project? 

Company-managed software

What type of project is the destination project?

Team-managed software

I used Bulk Change, then Move Issues

The filters I used were Parent Task and Status does not equal "done" or "will not do." 

The tasks were tasks, stories, operations tickets, research tasks, bugs, and I selected move the option to move child tasks. 

I created the new project, and have admin permission, the project is also open to anyone in my org. Currently, I can see 5 tickets I moved as a test before doing the rest of the tickets that are now now showing up. 

All of the tickets from the original project with the orignal parent tasks with status of done or will not do are still in the original project and it says they were updated today.  I'm not sure why that would be. I opened a sample of them and viewed their history, but don't see anything for today.

I don't see any of the 'missing tickets' in the updated within the last day search. 

[Trudy Claspill]

If you create a new issue in the destination project does the sequence number jump by ~150 from the last issue key sequence number you see in that project? If not, then the issues were never created in the destination project. If the number does jump, then the issues are or were there.

A Jira Product Administrator can go to Settings > System > Audit Log and check if there are entries there for issues having been deleted. Perhaps some process caused the issues to be deleted after they were moved into the project.

I'm pretty much out of ideas for things that you can check independently. My next suggestion would be to have your Jira Administrators open a support case directly with Atlassian Support. They would be able to examine log files for your instance which may help reveal what happened.

[Trudy Claspill]

The last thing I can think of, just to make sure we haven't miscommunicated on anything, is can you provide a screen image of the screen where you are attempting to search the destination project for the moved issues and not getting them in your search results?

Are you using either the Issues tab within the project?

Or using the general issue searching screen available from the Filters menu?

Some of the other tabs you might select within the project navigation will apply some filters automatically that could impact the results.