nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to allow issue movement but only to certain statuses?

Mridula Chintalacheruvu

As a JIRA admin, how can I restrict the below underlined action for users?

Issue status

You may have set up custom issue statuses as part of a workflow. If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue. You cannot arbitrarily change the issue status, i.e. the option to change the issue status will only appear if you are required to change it.

Accepted answers

Nic Brough -Adaptavist-

There's nothing here to "restrict". If you move an issue to a new config that does not match the old config, you must migrate it to the new one.

If you want to stop people moving issues though, just remove their "move issue" permission.

All comments

Nic Brough -Adaptavist-

There's nothing here to "restrict". If you move an issue to a new config that does not match the old config, you must migrate it to the new one.

If you want to stop people moving issues though, just remove their "move issue" permission.

Mridula Chintalacheruvu

Hi @Nic Brough -Adaptavist-,

Thanks for your answer. Allow me to rephrase my question:

I am looking to only allow users move from Issue Type (A,B or C) to Issue Type (D) with Status (I).
I want to disable users from moving issues to other statuses for Issue Type D.

Is there a way to do this?

Thanks,

Mridula

Nic Brough -Adaptavist-

No. A user can either move an issue or they can't. You can't restrict what status they choose if the workflows are different.

Mridula Chintalacheruvu

Thanks @Nic Brough -Adaptavist-!

Tom Hawkins

I found this page given similar challenge, in my case I have users who I wish to retain MOVE permission but for one specific workflow (within a project which I would like them to still be able to move to) there is a status where the workflow transition wouldn't allow them to select that status unless other conditions applied, but the Move usecase acts as a bypass to that currently. Hence I also found and voted on https://jira.atlassian.com/browse/JRASERVER-37136 as currently on server and https://jira.atlassian.com/browse/JRACLOUD-37136 as "to be" on Cloud. You may wish to do the same @Mridula Chintalacheruvu Not holding my breath though as low vote numbers for old issue Thanks for confirming the as-is @Nic Brough -Adaptavist- even if not what I wanted to find