You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Can you please suggest how can I restrict some issue types to some groups? I saw some suggestion using script runner, but I could not find how exactly to do that
Hi Kagithala,
Thanks, does this also prevent this issue type from being shown in searches and filters?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No.
Issue security simply hides issues from people. It does not affect create, search or reporting in any way other than hiding issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So in this case, for example, some people can create an issue, but cannot view it after creation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you can set an issue security scheme so that someone can create an issue with a security level they are not it, so they can't see the issue after the creation. Jira will tell them "issue created, but you can't see it".
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.
There's no pretty way to do this in Cloud. Cloud does not support Behaviours. (For server, you could use https://library.adaptavist.com/entity/restrict-issue-types )
You can stop people creating an issue type though, by using validators. The most basic implementation is to have two workflows, one for the issues you want to protect, and one for the ones you do not. In the workflow for the protected issue types, add a validator to the "create" transition, one that checks that the user has the right permissions.
I do not recommend doing this though, as it's ugly for the users - they enter all the data for their issue, then a validator says "you can't do this" and they have to start again with a new issue create.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.