nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Application Administration? Project Administrator? Please help

Warren McInnes

Hi all, I would like someone to help me understand the Admin levels in JIRA...I Think I am missing "Project Administrator"? (*See attached image) At our company there are two of us who are System Admins, How ever we have four "Solution Builders/Project Managers" and we require them to have a level of access where they can take control of project functions, These people are generally the "Project Lead"....However we do not want them to have access to the schemes (Permission/Notification), workflows, fields and screens...if that makes sense? So looking at the image(attached) I got when I was attending a JIRA Webinar this year, I see "Project Administrator" But do not see this in my Global Permissions, Where I do see System and Jira Administrators? Am I missing something? Could someone explain? Thanks, Warren

Accepted answers

Nic Brough -Adaptavist-

There are four levels of user in Jira

System admins - can edit ALL the system and Jira settings - specifically the stuff that is global and heavy - indexing, attachment paths, localisation, these guys can take the whole thing out. In Unix terms, they're "root" (and have all the rights of "Jira admins" below)
Jira Admins - can edit Jira settings, schemes, project settings (i.e. what schemes a project uses), user accounts, groups and so-on
Project Admins - can edit a project, changing versions, components and the users within the project (and Greenhopper boards if you've got that installed)
Users - well, they're users.

How they get these rights:

Users - they have an account
Jira and System administrators - are in groups defined in Global Permissions
Project Admins - are people who are given "project administration" by the projects permission scheme - this can be quite granular - you can end up with someone who is a project admin in ONE project. Note that Jira and System Administrators do NOT get this right automatically, you still have to include them in the permission scheme! (Some sites define a group of project admins and use that in the permission schemes, or directly include the admin groups in the permissions)

Sounds to me like you need to put your solution builders into project admins permissions. Might make sense to do this with a group and use that group in the permission schemes

All comments

Warren McInnes

http://imgur.com/Hs0llO2 (Image url, Couldn't find attach image)

Sakthi Balaji

Hi Warren, we need to add the members who wants to control the project details by default in the Project Administrator role in the Roles section. If we add them in the Project Administrator role, they can Administer the projects but cant have access on the permission and schemas

Nic Brough -Adaptavist-

There are four levels of user in Jira

System admins - can edit ALL the system and Jira settings - specifically the stuff that is global and heavy - indexing, attachment paths, localisation, these guys can take the whole thing out. In Unix terms, they're "root" (and have all the rights of "Jira admins" below)
Jira Admins - can edit Jira settings, schemes, project settings (i.e. what schemes a project uses), user accounts, groups and so-on
Project Admins - can edit a project, changing versions, components and the users within the project (and Greenhopper boards if you've got that installed)
Users - well, they're users.

How they get these rights:

Users - they have an account
Jira and System administrators - are in groups defined in Global Permissions
Project Admins - are people who are given "project administration" by the projects permission scheme - this can be quite granular - you can end up with someone who is a project admin in ONE project. Note that Jira and System Administrators do NOT get this right automatically, you still have to include them in the permission scheme! (Some sites define a group of project admins and use that in the permission schemes, or directly include the admin groups in the permissions)

Sounds to me like you need to put your solution builders into project admins permissions. Might make sense to do this with a group and use that group in the permission schemes

Warren McInnes

Where would I find this "Project Administrator role" Global permissions?

Warren McInnes

What is the difference between the Project Administrator and Project lead?

Nic Brough -Adaptavist-

As I just said, project administrator is done in the permission scheme for the project. It's not global.

Project Lead is a field that says "this person is the lead on the project". A common thing to do is say (in the project permission scheme, of course) "project lead has project admin rights", but it is optional

Warren McInnes

Oh i see, If I were to create a group call Project admins, Would the "Administer Projects - Ability to administer a project in JIRA." be the correct permission to add this group to? So that they have this "Project Administrator" status?

Nic Brough -Adaptavist-

Yes, you'll need add the permission in all of your permission schemes if you want it to be global though.

Warren McInnes

Who would then typically be the Project lead? Where would all the issues with "Automatic" Assignee's go to? Currently Project lead would get them?

Warren McInnes

Who would then typically be the Project lead? Where would all the issues with "Automatic" Assignee's go to? Currently Project lead would get them?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration