I have a couple developers looking at Jira to get our feed back on there games but I dont want certain developers to see every thing how do I control what users can and cannot see in our Jira.
Hi Ian
Thanks for your answer Zulfadli, however i have a slightly different opinion on this.
I would not recommend managing project visibility with groups and permission schemes. Firstly, because you will have to create a new permission scheme for each new project. Secondly, the ownership of managing the permission of projects would rest on jira admins and consider this overhead if you have 500 projects.
What we have in our organisation is one single permission scheme and i have added the project role say Developers in the browse project permission. This way the project admins can add relevant people to their project role - Developers and manage who can see the project.
On restricting the visibility of issues within project, i agree issue security scheme is the best option. Again on this, i would avoid a scenario where i have multiple security schemes one for each project(not a scalable option). What i recommend is that we have one single security scheme and when we define our security levels - we add project roles to it, so this way ownership of who can view what issues within a project again rests with project admin.
Rahul
You can limit what project they can see and what they can do by configuring the Permission Scheme. Moreover, if you would like them to see the same project but only certain issues, you can use Issue-Level Security.
Different schemes can be associated to different projects. Which would allow you to have Team A to only see project A, while Team B to only see project B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, could you be more specific in how to do this? I looked through the permissions and couldn't figure out which item I would need to change for say Project A to be viewable only to Team A, and Project B to be viewable only to Team B. As a test, I've changed "Browse project" to be viewable only to group "administrators", but everyone else can still view all projects after that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Collin
To have a restricted access to teams we need to create a global permission scheme after that we need to associate (apply) that permission scheme to the required project. so that only the particular group/users will have access to that particular project.
Below are the steps to do the same.
Creating a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Click the 'Add Permission Scheme' link.
In the 'Add Permission Scheme' form, enter a name for the scheme, and a short description of the scheme. Select Add.
You will return to the 'Permission Schemes' page which now contains the newly added scheme.
Adding users, groups, or roles to a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Locate the permission scheme you would like to update, and select Permissions in the Actions column to view the scheme.
Select the Edit link for the permission you wish to add to. This displays the Grant permissiondialog.
Select who to add the selected permission to, and click the Grant button. The users/groups/roles will now be added to the selected permission. Project roles are useful for defining specific team members for each project. Referencing project roles (rather than users or groups) in your permissions can help you minimize the number of permission schemes in your system.
Repeat the last 2 steps until all required users/groups/roles have been added to the permissions.
Deleting users, groups, or roles from a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Locate the permission scheme of interest and click its name to show the list of project permissions (above).
Click the Remove link for the permission you wish to remove the users, groups, or roles from.
Select the users, groups, or roles you wish to remove and click the Remove button.
Associating a permission scheme with a project
Choose the Jira icon > Projects.
Search for and select the project you want to change permissions for.
Select Settings to view the project's settings.
Select Permissions from the sidebar. This displays the current permissions scheme.
Click the Actions dropdown menu and choose Use a different scheme.
On the Associate Permission Scheme to Project page, select the permission scheme you want to associate with the project.
Click the Associate button to associate the project with the permission scheme.
Deleting a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Click the Delete link (in the Actions column) for the scheme that you want to delete.
The scheme will be deleted and all associated projects will be automatically associated with the Default Permission Scheme. You can't delete the Default Permission Scheme.
Copying a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Click the Copy link (in the Actions column) for the scheme that you want to copy.
A new scheme will be created with the same permissions and the same users/groups/roles assigned to them.
You can view the same on a confluence 'Managing project permissions https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great input …. thanks for information !!!!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
To have a restricted access to teams we need to create a global permission scheme after that we need to associate (apply) that permission scheme to the required project. so that only the particular group/users will have access to that particular project.
Below are the steps to do the same.
Creating a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Click the 'Add Permission Scheme' link.
In the 'Add Permission Scheme' form, enter a name for the scheme, and a short description of the scheme. Select Add.
You will return to the 'Permission Schemes' page which now contains the newly added scheme.
Adding users, groups, or roles to a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Locate the permission scheme you would like to update, and select Permissions in the Actions column to view the scheme.
Select the Edit link for the permission you wish to add to. This displays the Grant permissiondialog.
Select who to add the selected permission to, and click the Grant button. The users/groups/roles will now be added to the selected permission. Project roles are useful for defining specific team members for each project. Referencing project roles (rather than users or groups) in your permissions can help you minimize the number of permission schemes in your system.
Repeat the last 2 steps until all required users/groups/roles have been added to the permissions.
Deleting users, groups, or roles from a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Locate the permission scheme of interest and click its name to show the list of project permissions (above).
Click the Remove link for the permission you wish to remove the users, groups, or roles from.
Select the users, groups, or roles you wish to remove and click the Remove button.
Associating a permission scheme with a project
Choose the Jira icon > Projects.
Search for and select the project you want to change permissions for.
Select Settings to view the project's settings.
Select Permissions from the sidebar. This displays the current permissions scheme.
Click the Actions dropdown menu and choose Use a different scheme.
On the Associate Permission Scheme to Project page, select the permission scheme you want to associate with the project.
Click the Associate button to associate the project with the permission scheme.
Deleting a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Click the Delete link (in the Actions column) for the scheme that you want to delete.
The scheme will be deleted and all associated projects will be automatically associated with the Default Permission Scheme. You can't delete the Default Permission Scheme.
Copying a permission scheme
Select the Jira icon > Jira settings > Issues.
Select Permission Schemes to open the Permission Schemes page, which displays a list of all permission schemes in your Jira system and the projects that use each scheme.
Click the Copy link (in the Actions column) for the scheme that you want to copy.
A new scheme will be created with the same permissions and the same users/groups/roles assigned to them.
You can view the same on a confluence 'Managing project permissions https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html
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.