Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1-beta-2
-
Fix Version/s: 1.1-beta-3
-
Component/s: Integration - Ant
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
On vmbuild1, I found that one person with the correct permissions assigned for a project (as an administrator) failed to add an Ant project. They were given the option, and could enter the details into the form, but it failed with a permission error after that.
It succeeded for me, though I have all privileges other than System Administrator.
The project was being added to an existing group, via the button on the group page.
There are two possible causes:
- certain project types check the wrong permission. I find this the most likely - it's probably tied to the other user not being able to see the "add project" buttons in the left navigation as they only have that permission within certain groups. They are able to perform other operations on the group.
- the roles did not associate properly (though I tried recreating the group, and the user tried logging out/in again).
I'd like to confirm whether the first can be reproduced before checking the database for the second.
I'm sure it is fixed by the link between PG administrator and PG developer/user. Need to test