Destination project not appearing in bulk-move dropdown list

[Miles Monty]

Hi, I'm trying to bulk-move issues from a project to a new one that I created, but used the source project as the template, so all of the workflows and screens are the same. 

When I open the dropdown for destination project in the bulk-move flow, the new project doesn't appear in the list, along with a number of other projects in our space. 

What else can affect whether or not a project appears in the destination list, other than workflows, screens, and maybe also whether or not it's a company-managed project? 

Let me know if I can provide any further diagnostic information :) 

Cheers!

[Nic Brough -Adaptavist- · Accepted solution]

Bulk-<actions> respect the permissions for the projects.

My guess is that you do not have "create issue" in the target project.  (I think you have "move issue", otherwise bulk-edit would not offer it to you).

Note - good thought about company/team projects - I do not know if that permission applies the same to team-managed-projects.  I know it does for company-managed, as it does on server.  I would hazard a guess that you need "create" in team-managed projects as well, but I have not tested it.

[Miles Monty]

You sir, are a star. It was indeed the create issue perms. Thank you very much indeed!!