You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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. |
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.