JIRA Project Permissions schemes

[Jason Cottingham]

Our organization is new to JIRA and need basic advice on project permissions.  We plan to have a large number of projects and many of them can only be viewed by the members of the team on that specific project.  Our plan was to create a project scheme for each project team(may have 30 teams) and assign that scheme to each project.  Is this the best way to go?

[Alex Christensen]

We have a similar situation. Our approach is:

• One permission scheme used by all projects. This permission scheme is based on project roles.
• Each team has its own user group.
• Those user groups are then assigned to a project role within the appropriate project.

For example, we have Project A and Project B. We have separate teams, Team A and Team B.

• Team A will be assigned to the project role "Users" for Project A.
• Team B will be assigned to the project role "Users" for Project B.
• The single permission scheme is configured so that anyone in the project role "Users" for that project has specified permissions (like Create Issues, Edit Issues, Create Comments, etc.).

This approach makes managing the schemes a lot easier since all projects share one permission scheme. Of course, if different projects need to have different permissions for their users, you might need to make a few more permission schemes, but overall, it's easier to have a fewer schemes structured around project roles and have multiple projects share schemes.