Limit a group access to their issues and project

[Alain Goodarzi]

Hi,

I created a group of users.

I created a project for them.

I need to limit them to have access to their project and their tasks only.

The administrator could add issues to the project of course.

I tried a lot of tutorials and searched this community but couldn't find a solution.

need your help

thanks

[Alexey Matveev]

Hello,

I guess, your question means that this group of users has also access to projects, to which they do not have to have access. It means that the users in the group are also included in other groups or roles and these groups or roles have the Browse Issues permission in the projects where the users should not see issues.

You should remove the users from such groups and roles or remove these groups and roles from the project permission scheme of projects, which must not be seen by the users.

[Alain Goodarzi]

Thank you, As I mentioned I need to training resource, what is your suggestion?

[Alexey Matveev]

You can find more info here:

https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

[Joe Pitt]

JIRA works by GRANTING access. You can't restrict access. By default it grants access to the group used to logon (used to be jira-users but may be different on your version).  This is probably where you're getting the access from.

 The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.  Then I suggest you setup user roles for the various functions like, tester, QA, Browse Only, etc. Then you can create one permission scheme to cover almost all projects. The project admin controls which users are put in the roles.  This may be a big effort, but it will payoff down the road by making it easy to control access.

[Alain Goodarzi]

Thank you for your answer.

What is your document, tutorial or book suggestion to be able to follow how to do these. I have searched a lot and bought two training courses but main problem is they are out dated versions and menus are different and their contents are basic.

[Grigory Salnikov]

Hi!

You should try to set issue security level and use "Current Assignee" option. I think that will do the trick.

[Yogesh Mude]

HI @Alain Goodarzi

If you want to limit them to have access to their project and issues only then add the group and reporter to Browse project permission.