Menu
Currently we have mutiple projects sharing a JIRA instances. We want to make it such that the users only view the projects that they are doing testing.
But however we are currently groupging these users to the standard grouping jira-users.
What is the best way to filter out JIRA project that only certain users can see and access
712
Go to Jira settings > Issues > Permission schemes. Find the permissions scheme associated to the relevant project, and click Permissions. Click Edit, choose Project Role, and select the Browse project role we previously created.
Creating Filters in Jira In order to create a filter, go to Issues > Search for Issues to define your search. Make sure to execute it to confirm that the syntax is correct. Finally, click Save as and choose a name for your new filter. That's all there is to it!
JIRA permissions JIRA works by GRANTING access. You can't restrict access. By default, it grants access to the group used to logon (see Global permissions to see the "can use" groups and admin groups).
Personally I'm all for project roles. I have a general permission scheme that allows all users/groups defined in project roles to browse the project, which leaves the project administrator/manager to define which groups can view their project. So by removing or adding jira-users (default group that a user would have to be a part of to even log into JIRA) to thier project's "users" project role, the project manager can control if all users can view their project or not.
98
You should create special Groups of users for each project you have... you can have more than one group, something like "project1_developers", "project2_observers" for better organization.
You alson combine these groups with the Project Roles to define into each project what kind of access each group should have.
Make a Permission Scheme to set of permissions to one project. Something like this:
Browse Projects -> Group (project1_admins, project1_developers, project1_users, project1_observers)
Create Issues -> Group (project1_admins, project1_developers, project1_users)
Move Issues -> Group (project1_admins)
You can use your Project Roles here too... but I prefer to set everything with groups.
Finally, you can use Issue security schemes to define who can and cannot view issues. Issue security schemes implement a number of security levels which can have users/groups assigned to them.
Hope that can help.
31
Totally agree with Brian: Project Roles are the way to go, else you end up with too many Groups. Role membership is local to a project. Groups are global.
Totally disagree with Balarami: security levels should be used very sparingly and on small percentage of the issues (on exception basis).
32
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
