Issues missing after migration to new project

[Laszlo Kahr]

I'm using Jira Cloud and did a bulk move operation in order to migrate issues from a next-gen project (TCC) to a newly created classic project (TCLOUD). After all the tickets were processed I wanted to check them in the new project. But they all seem to be disappeared. 

After my first panic I searched for similar cases and found one that was exactly the same: https://community.atlassian.com/t5/Jira-Software-questions/Tickets-vanished-after-migrating-to-a-new-project/qaq-p/1414000

In that case the user (greg_bryant) wrote in his resolution that he initially used the default issue permission scheme, which wasn't letting him view the issues auf bulk moving them.

Unfortunately it was not described what exactly there is to change in order to make the issues reappear for me.

I also tried to search for the missing issues as I still know the summary/description of some of the issues from TCC. But I find no results in the (advanced) search. Also I can't even search for / select the TCLOUD project while searching ("The value 'TCLOUD' does not exist for the field 'project'."). But I see the project in my project list and also can edit the project settings of TCLOUD (as I am a site admin). 

Help would be really appreciated!

[Benjamin · Accepted solution]

Check the browse project permission in the permission scheme. Check the roles or groups that are assign that permission. Then assign yourself and anyone else in your team that role. After that, you should be able to view and search issues in your project.

Hope this helps.

[Laszlo Kahr]

Thank you very much, Benjamin!

When I initially created my new classic project (TCLOUD) only the user-role "Administrators" was set for the project. But with the “Default software scheme” (also set by default) this user-role had no permission to browse the new project – which I find irritating but probably is the fault of myself or respectively the site-/jira-admins who defined it that way.

But what I find really strange from Jira side:

Why does Jira show messages like "Can't find link" or "TCLOUD' does not exist" when only the correct user-role was not selected. This really stressed me out and I would have appreciated if Jira instead said something like "will not show you the link (but issues exists)" or "TCLOUD does exist but you are not allowed to view it".

[Benjamin]

Glad it all worked out!