Move issues

[hoongchun.lim]

Hi, is there any way to restrict users from moving issues out of a project while still allowing them to move issues within the same project?

[Marc - Devoteam · Accepted solution]

HI @hoongchun.lim 

Welcome to the community.

Don't grant the users move permission on the project permission scheme.

Then users can't move issues, but this means they can move them to other issue types in the project as well.

If you mean by moving changing status, this is another permission, this is the Transistion permission.

[Mirek]

Hi @hoongchun.lim 

By default I guess there is no easy option to restrict this in specific project. There is a Move Issue permission but it does not distinguish scope withing project or other. Once user would have Create/Browse permission in second project he would be able to move to it, but not sure if this is an ideal solution if there are many projects.. 

Overall I think that changing issue types (e.g. from Task → Bug), you don’t need to "move" issues permission at all - just change the issue type (but you have to make sure that configuration in both types are same)

[Brock Rhett]

Thank you so much for the detailed info.

[hoongchun.lim]

@Marc - Devoteam , Thanks for the suggestion.

I plan to implement a workaround by restricting the "Move Issue" permission at the project level to prevent users from moving issues across projects.

Instead, I’ll create a popup modal with issue context that allows users to change the issue type within the same project via API.

[Piyush Annadate _ACE Pune_]

Hello @hoongchun.lim ,
Welcome to the Community !
Jira does not natively provide granular permissions to restrict only cross-project moves while allowing within-project moves
Permission to move issues from one project to another or from one workflow to another workflow within the same project. With this permission, users can only move issues to a project where they have Create Issue permission.

The "Move Issues" permission in Jira controls whether a user can perform the Move operation on issues. This includes both:

• Moving issues between projects, and

• Changing the issue type within the same project

When you perform a Move operation in Jira and change the issue type for the destination project, Jira will prompt you to select new statuses based on the workflow associated with the selected issue type in the target project.

If you do not change the issue type during the move, Jira will apply the workflow assigned to the current issue type in the destination project (or in the same project, if you're moving within it).

Note:

• When moving an issue to another project, the issue will adopt the workflow and transitions defined for the issue type in the destination project.

• When moving an issue within the same project, you can change the issue type, and the issue will follow the workflow associated with the new issue type within that project.