Hi! In our organization we have a Jira Software project in which 4 teams collaborate on issues.
One of those teams - the Compliance team - occasionally creates highly sensitive issues. They would like these sensitive issues to be visible only to their team and not to the other teams. However, this is not always the case - they only need this restriction for specific issues that arise from time to time. For most of their issues, the other 3 departments should be able to see them.
Given that we have a dedicated user group in our Jira Directory for each of the 4 departments, including the Compliance team, what is the best way to achieve this selective visibility? Can I configure permissions in such a way that the Compliance team can choose which issues to restrict from view for the other teams while keeping the rest visible?
Hey Leons, I think best way to protect your classified issues is issue security. Fist you need to create issue security scheme, you can add your Compliance team one by one or as user group. You can add a new issue type to your issue type scheme for this sensitive issues and you schould use different workflow for this issue type. Then in the create transition you can set up issue security with post function.
@Ezgi Bayındır hey there! Thank you for the reply.
I have created an issue security scheme as you suggested. And I have added an issue security level to it. I have associated the issue security scheme with the target project.
But why can't I choose that issue security level now? It just doesn't show any options. I even added more security levels to it and I have project permissions to set security levels but still nothing. I'm confused.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Leon Gumba
There is a permission
Only those on that permission can change the security level.
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Aaron Pavez _ServiceRocket_ thank you for the reply!
Yes, this setting is fine for me. As I stated in my previous reply, I do have project permissions to set issue security.
But the padlock icon is still missing from the already created issues. And the Security Level field doesn't show any options inside the issue creation screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ezgi Bayındır & @Aaron Pavez _ServiceRocket_ hey, I have actually figured this out with the help of one of my colleagues.
Turns out you won't be able to see the padlock icon and Security Level field values if you're not the part of the Issue Security rule. I have added myself to it, and now it's visible. But now I should actually remove myself since I shouldn't be using that security option anyway, it is there for other departments to use.
Thanks!
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.