Trying to make myself as bug supervisor of my project oopses
Bug #438985 reported by
Ursula Junque
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Graham Binns |
Bug Description
Steps to reproduce:
1) Go to launchpad.dev and login as a regular user (without supercow powers)
2) Create a project
2) Go to bugs.launchpad.
3) Boom! OOPS-1367G1058
UserCannotSub
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in malone: | |
assignee: | nobody → Graham Binns (gmb) |
milestone: | none → 3.1.10 |
Changed in malone: | |
status: | Triaged → In Progress |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
My fault! It's concerning that no tests broke. I incorrectly used 'is' to compare the user and person, when I should have used '=='.
Reading the view code also revealed another issue: there is a permission conflict. When setting the bug supervisor, you can set it to any person, or a team you administer. This implicitly adds a structural subscription for them. In other places you can only subscribe *yourself* or a team you administer. The latter restriction is now implemented in the model, so attempting to set the bug supervisor to another non-team person will fail similarly. I'm not sure how best to resolve this one.