I want an issue within a project to be visible only to the team I choose.
Hi @Berkay Aşık and welcome,
as @Shalini Pradhan mentioned: User Permissions are set on a project level. However there is also the "Issue Security Scheme"-Feature (editable under Settings - Issues - Issue Security Schemes). Those "[...] allow you to control who can and cannot view issues. They consist of a number of security levels which can have users/groups assigned to them."
Maybe have a look at them, if this suits your usecase of "restricting view of Issues to certain Users / Groups"
Kind regards
To make it more clear:
This enables you to have basic permissions , regarding all your Users (Permission Scheme + Groups) and control over individual Issues (Security Schemes).
You still need to set the right permissions for the project.
KR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Berkay Aşık ,
Good day!
A user's access to a project depends on the permissions and the type of project that we are dealing with.
COMPANY MANAGED PROJECT
In company-managed projects, to restrict/provide access, we need to manage this via project settings -> Permissions -> Browse permission. Browse permission allows people to view the project in the Projects directory, and view individual issues in the project and while searching Jira. You can refer to this document for more details.
Here permission scheme plays a role where either you can have separate permission schemes for different projects OR a common permission scheme for a few or all projects, depending on your requirement.
Also please make sure Any logged-in user ( any user who logs in to your instance can view the project ) is not added under Browse permission for your company-managed projects.
TEAM MANAGED PROJECT
For a team-managed project, you can determine a person's permissions in your team-managed project in 2 ways.
To restrict/provide access, we need to manage this via project settings -> Access and accordingly add people and assign roles ( Administrator, Members, or Viewer ) and select the access level of the project ( Open, Limited, or Private )
Here, we do not have any permission scheme concept. All permissions need to be handled individually in separate projects.
You will find more details in this document: Team-managed project permissions
In your case,
Thank you :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online 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.