Converting public +snap to private in one step leads to an OOPS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Tom Wardill |
Bug Description
When attempting to convert a public +snap to a private one you have to do a number of things:
1) add it to a project (maybe private),
2) move it to a private team, and
3) mark it private.
If you attempt to do this in a single +edit update we throw an OOPS (OOPS-70de1366bbed7ed4bbdda9c3668f7e6e for example) indicating that a private snap cannot belong to a public team.
It is possible to get to the desired configuration in three steps:
1) add the project and save,
2) mark it private and save, and
3) move it to the private team and save.
I assume it should at least tell you the issue and fail rather than throwing an OOPS, but as the final combination does pass validation it feels like we should be able to get there in one.
Related branches
- Colin Watson (community): Approve
-
Diff: 70 lines (+36/-1)3 files modifiedlib/lp/code/model/branch.py (+3/-1)
lib/lp/snappy/browser/snap.py (+4/-0)
lib/lp/snappy/browser/tests/test_snap.py (+29/-0)
- Thiago F. Pappacena (community): Approve
- Ioana Lasc (community): Approve
-
Diff: 55 lines (+33/-0)2 files modifiedlib/lp/snappy/browser/snap.py (+4/-0)
lib/lp/snappy/browser/tests/test_snap.py (+29/-0)
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Tom Wardill (twom) |
Changed in launchpad: | |
status: | Triaged → Fix Committed |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |