Why a user can`t move issues to another project?

[Rosana Casilli]

Hi all!

I am trying to figure out why an user cannot move issues to another project.

The user in project A, wants to move the issue to Project B, but Project B is not shown when I try to move the issue Why is that? all the other projects are shown but Project B it is not.

Can you help me please?

Thanks in advance,

Ro

[Deepanshu Natani]

Hi @Rosana Casilli 

Can you confirm that this user has permission to create issues in Project B? (A user can only move issues to a project they have the create permission for.)

[Rosana Casilli]

He is a customer for the project B. 

In project B permission to Move issues "Service Desk Customer -portal access" is set

[Yevgen Lasman]

The Move Issue permission is not sufficient, the user should have "Create Issue" permission in the "Project B". This is because technically there are two operations: create issue in Project B with the issue data from the Project A and (re)move issue from the Project A.

You can find more details about each project permission here, and "Move Issue" says

Permission to move issues from one project to another, or from one workflow to another workflow within the same project. Note that a user can only move issues to a project for which they have Create Issue permission.

[Rosana Casilli]

Thank you!.. I see that the service desk customer have edit, create, delete move permission. 

But still the user can't move anything.

[Rosana Casilli]

In fact.. I tried to access as this user and he can't see the any jira service desk project but his. Only Jira Software projects