Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to allow issue movement but only to certain statuses?

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

 

Issue statusYou 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.

2 answers

1 accepted

1 vote
Answer accepted

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

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.

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 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

208 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you