I have a group of users who should only be permitted to see a certain group of tickets based on how one field is filled out. Anyone in the company can see those tickets, but this group of users shouldn't be able to see anything else.
These "special tickets" are in a Jira project along with other kinds of tickets. So doing an issue level security scheme from my understanding wouldn't work because that only works at the project level.
Is there any way, through project role groups, permission / issue security schemes, boards / filters, or some other way, I can limit this group to only seeing certain tickets?
Hi @Michelle Rose ,
I think this problem needs an upside down issue security using. Add people from the restricted group to a new group and make sure that they are not in the group that you are using for application access. But also give them application access so that they can access the system. In this way, we will keep this group separate from other users. You should create an issue security scheme and add two levels. Use application access group and group for restirected people for level one and use only application acces group for level two. You should set the issue security level as level 2 in the issues that you want the restricted group not to access.
Best,
Ezgi
@Ezgi Bayındır Thank you so much. How can I specify which are the issues that I don't want this group to access? Can I do that via specific fields?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
More specifically, the way it works right now is for a specific field if certain options are chosen those are the only tickets we want this group to access.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use Automation for set issue security and add condition for that specific fields option. You can look this similar example
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Michelle Rose
If you wish to apply security selectively to specific issues, consider using issue security levels. Refer to the documentation below for instructions on assigning an issue security level to a particular issue type.
https://support.atlassian.com/jira-service-management-cloud/docs/create-security-levels-for-issues/
Regards,
Geethanjali.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Geethanjali Katagani Thanks but I don't think this gives me what I am looking for. It's not about restricting issues to only certain people, it's about restricting a group to only see certain issues - does that make sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.