Adding a user to Roles field does not give them Administrator capability

[Nari Man]

I have a project A, where I add a user to the Roles field as admin. The user does not get admin access to that projects. 

I add the same user to another project B and he has Admin access to that project. 

Project A and B use the same Permission scheme. 

I can not explain this at all. What is going on? Anyone who can help?

[Nic Brough -Adaptavist- · Accepted solution]

This is probably a case of checking carefully.  Go into project A, and find its config screen.  Find the permissions bit and open it up from there, so you can check what the rules for "Project Admin" say.  I'm doing it this way because it guarantees that you land on the permission scheme it is definitely using.

Now, note down the rule for admin (does it say "Role: Admin" for example?).  Now go back to the project admin screen and descend into the Users and Roles section to re-check that your user definitely meets the rule (Assuming it was a role based one)

[Nari Man]

Do you mean that in the Administer Project section I need to have "Project Role (Administrators)"? Until now I only have the "JIRA-Admin" Group. 

[Nic Brough -Adaptavist-]

I'm not sure what you are saying there. What you need to look at is the line that says "Administer project". What does it say next to it?

[Nari Man]

It says jira-admin.

[Nic Brough -Adaptavist-]

No, it does not. It says more than that. Could you give us everything it says there.

[Nari Man]

Screenshot 2015-02-19 10.00.40.png

[Nari Man]

Added the screenshot.

[Nic Brough -Adaptavist-]

Right, so it says "Group: jira-administrators" and "group: jira-scrummasters" That means you are not using roles at all for this permission. You're using groups. Forget the roles and add the user into the right groups.

[Nari Man]

I added the Project Admin role in the Administer Project section and it solved the problem. thanks