Project Lead and Project Role=Administrator role can not access Project Administration

If people are the Project Lead for a project, and also added to the Project Role of Administrator, should they not be able to access the Project Administration?  For some reason, this is not happening.

3 answers

My understanding is that project roles have no innate privileges, it depends on the permission scheme for the project.  One would generally expect that the administrator role have "Administer Projects", but it's certainly not guaranteed.

In Permission Schemes, editing the scheme associated with most projects.  For Administrator, when you Edit, the Grant Permission dialog appears.  Permission = Administer Projects.  I selected Project Role=Administrators.  However, when I use the Permission Helper, it says that a person who is in the Administrators Role does not have Administer Project Permissions.  It works for some people, but not others and the projects are using the same permission scheme.  Any idea what's up?

Nothing comes to mind offhand.  Unless maybe you require Browse as a prerequisite for Administer.  Can you paste screen shots (redacted as necessary/desired) of the Permission Helper analysis of the user, as well as the project's role page and the permission scheme?

Permission Scheme.png

Here is the Permission Scheme

Maybe this is the problem.  I thought that adding people to the Administrator Project Role would enable them as Admins for all projects.  Do you also have to add them again on each project?

Yes,

Roles are defined globally, but work on a project level.

Users belong to a role on a project level - that's what they were intended for (you can use one permission scheme but have totally different sets of users for each project).

If you want to be able to add a "global" set of project admins, that aren't JIRA admins, I'd create a group, and explicitly add that group to the permission scheme.  That will give members of that group "Administer Projects" independent of the individual project role membership.  The role membership is, by design, for individual project management.

Alternately, you could add that group to each project, but that will enable 'local' project admins to also remove them, should any exist.

0 vote

Maybe.   Check the project permission scheme to see who that grants project administration to.  You might not have "project lead" or "role project administrator" in it.

Was this resolved? we are seeing the same thing so curious

Yes, as per @Jeremy Gaudet 's answers.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

59 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you