I am seeking advice on a user administration methodology that allows project admins to administer their own projects without Jira Admins constant involvement.
Here is the environment: We havhe one project that has 300 users spread across 10 user groups. At the moment, Jira Admins must add/remove users to those groups, which is time-intensive. We are looking to off-load this responsibility to the Project Admins, let them manage their own users (after Jira Admins create their accounts) because we plan to increase the user base for that project from 300 users to 3000 users.
We also have 200 projects in our environment that would be affected by global changes.
User Groups:
+ is being used to manage the project effectively.
- it's requires Jira Admins to manage the groups, which is not scalable.
Roles:
+ Create new roles that can be used to by Project Admins to manage their own users' access to different parts of their project.
- these new roles would be seen by all projects, so it's not an ideal way to administer one project and affect 200 projects.
Components:
+ Use Roles to get users into the project, then Components to break the project into smaller groups that are managed by the Project Admins.
- cannot add users to Components, just Leads. So it wouldn't really control the users, just gives Issues a new parameter for sorting (this is how I understand Components, not sure if there is more functionality built in that I haven't used).
Has anyone developed method that allows Project Admins to manage their users, and also break them into sub-groups, without involving Jira Admins? Thanks all!
