Closed
Bug 512077
Opened 16 years ago
Closed 16 years ago
Admins loose rights after successful upgrade from 2.20.1 to 3.4.1
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: nicolai.kamenzky, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.13) Gecko/2009073022 Firefox/3.0.13
Build Identifier: 3.4.1
Our Bugzilla 2.20.1 hosts many products. If you are in the admin group you can edit all these products.
After we upgraded to 3.4.1 - everything went fine - some of the admins cannot edit some products anymore. That means they do not get all products listed on the respective administration page.
The products not listed are exactly those for which the admin-user is not allowed to report bugs. To be specific each of our products have one and only one group associated in the Group Access Controls with Entry checked and Mandatory / Mandatory. For all other groups no checkboxes are checked and NA / NA is used. In this way our products are associated to one and only one group. If the admin-user is not a member of a certain group then the associated products are not listed in the administration page.
I expect that a user of the admin group would also get in 3.4.1 all products listed in the administration page.
I verified that by installing 3.4.1 with an empty database. Then I did the following:
1. I logged in with the administrator account created when running checksetup.pl.
2. I created a new group which is used for bugs. (I did NOT add the administrator to that group!)
3. I created a new product.
4. In the Group Access Controls for the new product I checked Entry and set Mandatory/Mandatory for the newly created group in step 2. (Nothing else I set.)
5. I navigated to Administration -> Products and got the newly created product listed.
When I do exactly the same in our upgraded Bugzilla step 5 fails.
For the upgrade I used checksetup.pl and recode.pl. There where no errors. All data was migrated correctly which I verified by doing some comparisons between our old and the new Bugzilla.
If I remember correctly I also saw the same issue in Bugzilla 3.2.2 after migrating our 2.20.1 database to it.
I think the DB was somehow migrated incorrectly. I also saw in our upgraded Bugzilla that the new per-product rights are not working. Maybe the DB migration scripts have a defect with a larger impact. But let us talk about that later...
Reproducible: Always
Comment 1•16 years ago
|
||
This behavior is intentional and has been implemented in Bugzilla 3.0, see bug 189627. Being an admin doesn't give you full power. If the admin is not in the group associated with a product, this means he is not allowed to edit this product (and components, milestones, and versions) at all, which is why we omit it from the list. If you want your admin to be able to access all products, don't remove the group inheritence between the admin group and the groups you created.
The reason you don't see this problem when you create a new group is because Bugzilla automatically sets inheritence. So Bugzilla is working as expected.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
| Reporter | ||
Updated•16 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Version: unspecified → 3.4.1
Comment 2•16 years ago
|
||
Don't reopen the bug. Read my previous comment.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•