Hello - I am working on a Jira Work Management cloud project that contains information that we would not like everyone to have access to. The issue is that we also need people to be able to view tickets that they are needed for within said project. I am looking for a way to allow the core group of people working on the project to maintain full access, permissions, and visibility of the project while restricting access to anyone else to only see tickets that they are assigned to.
My first thought was to create two groups (one for the team and one for everyone else) but we have a lot of people that we would need to give the restrictive role to. I would then create a new permission scheme that would allow me to do what I described above. Is this the right direction to go in? Is what I am describing even possible in only allowing certain people access to view the project?
Thanks!
Hello @Alex John
Is the project a Company Managed project or a Team Managed project?
If it is a Company Managed project, take a look at Issue Security Schemes.
https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
You can use that to set a Security Level on each issue making it visible to only the core group or to the core group plus the current assignee.
This is great, I didn't realize this was an option! It is a company-managed one. I guess I could just make a role within a new Security Scheme of "Contributor" which would only allow someone outside of the project team to see or interact with tickets that they themselves?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I recommend that you go through the Atlassian University self-paced training concerning Issue Security to get a deeper understanding.
https://university.atlassian.com/student/catalog/list?search=issue+security
I also recommend that you set up a test project to work out what you need before trying to apply it to your live project.
You need to figure out how you designate the "core team" vs. the "contributors" that should have limited visibility. These are your options that you can use to specify who can see an issue:
Are your "contributors" and "core team" contained in discreet user groups or project roles?
There are multiple ways you could set up issue security levels depending on how you use groups vs. roles. I can't tell you "do it this way" and guarantee that will work without knowing how your "core team" and "contributors" are being assigned to those groups and/or roles.
Another thing to think about is can a "contributor" create a new issue? Should they be able to see issues they create even if they are not assigned to them?
You'll have to look at how you want to set the security level on each issue; whether it should be able to be set by the users or if you want to set it automatically, and allocate the Set Security Level permission accordingly.
And note that there is no automatic setting of the security level on issues that already exist. If you implement an Issue Security Scheme you will need to set the security level for the existing issues. An issue that has not security level set will be visible to all users who have the Browse Projects permission for that project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the in-depth response, and yes I am definitely working on this in our test environment. I believe what I am looking to do is to create project roles for this and similar subsequent projects (Contributor/Core Team) as the actual people in them may change in the future. The contributors don't need to make any tickets as the project team has already determined the exact work that needs to be done, they just need to be able to see and work on the tickets assigned to them.
Great tip about the security on existing issues. I think I just want binary access where people who are part of the project team have full visibility and access for the project and anyone else has none (unless they are a contributor). I'm checking out that video you linked today.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wanted to follow up with how I did this:
At this point I am able to assign tickets from the project to any Jira user and they will only be able to see tickets within the project that are currently assigned to them. Compliance Team Members and Admins will be able to browse the entirety of the project without restriction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill ,
I'm encountering a similar issue to what Alex described. However, I'm working on a Team Managed Project in Jira Work Management (Cloud).
Since I noticed you made a distinction when replying to Alex based on whether he was working with a Company Managed project or a Team Managed project, I'm curious if you have resources available regarding a solution for Team Managed Projects.
In our Project, we're collaborating with two clients in different countries. We aim to configure different roles for them to view the information specific to each of their countries separately.
Is is possible to achieve this within the Team Managed Project settings, or whould you advise us to create separate boards?
Thank you for your assistance with this matter!
Best,
Irini Sfirakis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Irini Sfirakis
The issue security options are different for Team Managed projects. Refer to
If you have additional questions on this topic, please start a new Question post to ensure your questions get maximum community visibility.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Trudy Claspill ,
Thanks you so much for your prompt response!
I've reviewed the resources you kindly shared, and I've noticed that we have not configured the "Restrict Issue" setting (see screenshots below).
While attempting to find out how to configure this setting, I came across a thread you replied to (https://community.atlassian.com/t5/Jira-Software-questions/How-to-enable-restriction-for-issue-ticket-of-Jira-Work/qaq-p/2243301) where you mentioned that this configuration was not available for Team Managed Projects. Perhaps this has changed since then. Could you please clarify?
Best,
Irini Sfirakis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Irini Sfirakis
Good find! I had forgotten about that.
Issue Restriction is not currently available for JWM Team Managed projects. There's a change request about that here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill ,
Thanks! I've voted and I am watching the progress of this change request.
Best
Irini
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.