Use multiple permission models in JIRA project management to isolate and manage configurations of multiple project Modes

Use multiple permission models in JIRA project management to isolate and manage configurations of multiple project Modes

1. Add a user

Common users need to fill in the user name, password, Confirm Password, full name, Email address;

LDAP users only need to enter the user name, full name, and Email

11194
Obo

11195
Bai botao

11196
Liu Kai

2. add three new user groups corresponding to the Default User Group

New user group for Default User Group
Purpose

Jira-administrators glts-administrators Management User Group

Jira-developers glts-developers execution User Group

Jira-users glts-users Common User Group

3. Add a user to the corresponding user group

User Group member

Glts-administrators 11194

Glts-developers 11194, 11195, 11196

Glts-users 11194, 11195, 11196

4. add three new project roles to correspond to the three new groups created in step 3, and add the three new groups as the default groups of the three new project roles.

Default User Group corresponding to the project role

GLTS-Manager glts-administrators

GLTS-User glts-developers

GLTS-Worker glts-users

5. Add new user group permissions to global Permissions

The JIRA permission corresponds to the default user group.
Corresponding New User Group

JIRASystem Administrators jira-administrators
(* Glts-Manager)

JIRAAdministrators jira-administrators
(* Glts-Manager)

JIRAUsers jira-users
Glts-User

BrowseUsers jira-developers
Glts-Worker

CreateShared Objects jira-users
Glts-User

ManageGroup Filter Subscriptions
Jira-developers glts-Worker

BulkChange jira-users
Glts-User

PS: we do not recommend
JIRA SystemAdministrators,
JIRAAdministrators
Grant permissions to the glts-Manager User Group. The entire system uses an administrator account to manage all projects.

6. Copy the default permission management model and rename it as the specified name, for example, "manage the permission management model of the team"

7. Follow the default permission management model to grant different permissions to inaccessible project roles.

Corresponding new project role default project role

Glts-manager Administrators

Glts-user developers

Glts-worker users

8. Add a new project management class, such"Management Enhancement class". This step is not required. Adding a project category is only for the convenience of Project classification management.

9. Add a new project, such as "power plant management upgrade", keyword "grglts", select 11194 as the project owner, and select "Management Promotion Group permission model" as the permission model ". After adding the project role, modify the default group corresponding to the project role member.

10. In user management, you can set the current user's project role to operate on newly added projects.

11. In user management, set the project roles of the newly created three users to operate on the newly added project.