issues are missing after bulk moving

[T. K.]

I moved a large amount of issues from one project to another and now those issues are gone.  please help!!

[T. K.]

thank you everyone for your quick responses.  We managed to figure out what happened.  As embarssing as it is we overlooked the fact that when bulk moving the issues get renumbered.  Due to the large amount of issues it got confused. thank you again and Happy New Year.

[Jack Brickey]

ha. well none of the rest of us ever doing anything embarrassing like that! ;-)

glad you got it figured out.

[Nic Brough -Adaptavist-]

Nope, never done that myself, ever.  At all.  Ever.  Honest.  ;-)

[Adrian Chng]

Hi there, I have the same problem - I have just moved a bunch of issues from Project A to Project B and now they're not visible at all. Can you share what you did to find the issues again?

[Nic Brough -Adaptavist-]

Try just putting in the old issue key into the quick search.  It will redirect you to the new place it has landed.

Unless you don't have permission to see it in the new place!

[David Taylor]

I was moving issues to a new project and this happened to me too!  The Epic showed up immediately in the Kanban board, but none of its child issues did!  I tried the same with a Task, which showed up immediately, but the none of its subtasks did!  

I realized if I remove the parent issue and then reassign it, then the issue will immediately show up in the new project.

So this is how I solved it -- an issue trigger automation that does just that for each child and subtask.

- manual trigger
| - branch 
|   |- children
|   |- edit child to remove parent
|   |- set child parent to trigger issue
| - branch
|   |- subtasks
|   |- edit subtask to remove parent
|   |- set subtask parent to trigger issue   

Then go to the parent issue (the one that IS showing up in the board) and trigger the automation.  Voila! If you have Epics > Tasks/Stories/Bugs > Subtasks.. then this only works one level at a time. You can use this automation on both an Epic or a Task/Story/Bug, but it only works on direct descendants. Just repeat if you need to.

[Gina Leuty]

This happened to me as well, but it was another user error situation. I did not have a status mapped on the new project. Once I mapped that status to the backlog, my missing issues were visible.

[sadia hanif]

Hi,

I have moved bulked moved issues from one project to another and cannot see them in either .Can someone advice please.

Thanks,

Sadia

[Nic Brough -Adaptavist-]

If you can remember one of the old issue keys, then search for it - when Jira moves an issue, it retains a pointer from the old key to the new one.

Another thing that might hide a moved issue is permissions and security - check you have browse permissions in the target project and if there is a security scheme in place.

[Jack Brickey]

Yes reindexing is automatic on cloud. So when you say they are missing how have you searched for them? Can you, if you have not, run the following query in the issue search

project = ‘new project’

if the results are not sorted by issue key then sort such that the newest is at the top. Assess if the newly moved are there. 

[Alexey Matveev]

Hello,

If you are on Jira Server/Data Center try to reindex your Jira instance.

[T. K.]

thanks for your help but I am on the online cloud version and dont see a way to reindex.