Changing default bug visibility of a project to private triggers database constraint
Bug #266890 reported by
Ursula Junque
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Brad Crittenden | ||
Bug Description
When trying to set the default bug visibility of a project to private (in project/
This affects only lp admins.
Steps to reproduce (with sample data):
1) Enter http://
2) Check the "Private bugs" checkbox
3) Click on "Change"
4) Oopses with the error: IntegrityError: new row for relation "product" violates check constraint "private_
This bug may be related to bug 125803.
Recently: OOPS-1011EB191
Related branches
lp:~bac/launchpad/bug-266890
- Aaron Bentley (community): Approve (code)
-
Diff: 112 lines (+50/-12)2 files modifiedlib/lp/registry/browser/product.py (+21/-12)
lib/lp/registry/browser/tests/product-views.txt (+29/-0)
| Changed in launchpad-foundations: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| description: | updated |
Revision history for this message
| Brad Crittenden (bac) wrote | #1 |
| affects: | launchpad-foundations → launchpad-registry |
| Changed in launchpad-registry: | |
| milestone: | none → 3.1.11 |
| Changed in launchpad-registry: | |
| assignee: | nobody → Brad Crittenden (bac) |
| Changed in launchpad-registry: | |
| status: | Triaged → In Progress |
Revision history for this message
| Brad Crittenden (bac) wrote | #2 |
| Changed in launchpad-registry: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Actually I don't think think this bug affects LP admins but only affects LP commercial admins, who have fewer privileges. The LP admins see a warning and an option to set the bug supervisor while an LP commercial admin does not see those options and is allowed to submit the change resulting in the db constraint and OOPS.