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

Do not allow moving an issue to a certain project

Hi Team,

Is there a way I can unable moving an issue from one project to a specific project?

I have a project called 'inbox' and generally I would like to allow members to move issues from this project however I have a specific project to where I would like to ban this option. Is there a way to restrict the move option to a specific project?

Thanks a lot!

2 answers

1 accepted

Hi, as far as I can tell, that's not a possibility. In order to move an issue the user must have move permissions on the origin project and browse and create on the destination one. And that's the only thing you can play with since the move operation isn't a transition, therefore you can't make use of conditions and validators to avoid users moving issues to the other project

Thank you, I was afraid to hear that. 

0 votes
John Funk Community Leader Nov 23, 2020

Hi balazs.chikan@ibm.com  - if you change the permissions for the project so that only you have Browse Project, then no one else can see the project.

Or you can just change the Create Issue permissions just for you 

Thanks a lot John. Unfortunately both projects are used by all Jira members. The only think we need to restrict is to move issues between the projects as they have different workflows and information is keep getting lost. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

299 views 9 7
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