Can file an Unembargoed Security bug when default_private_bugs is set
Bug #1004702 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Ian Booth | ||
Bug Description
The check for security does not distinguish between embargoed security and unembargoed security. When .private_bugs is true, public and unembargoed security are not legitimate options. They should not be shown to user either.
Related branches
lp:~wallyworld/launchpad/file-private-bug-1004702
- Curtis Hovey (community): Approve (code)
-
Diff: 180 lines (+76/-12)5 files modifiedlib/lp/bugs/browser/bugtarget.py (+1/-1)
lib/lp/bugs/browser/tests/test_bugtarget_filebug.py (+38/-4)
lib/lp/registry/tests/test_information_type_vocabulary.py (+27/-3)
lib/lp/registry/vocabularies.py (+7/-3)
lib/lp/testing/factory.py (+3/-1)
| Changed in launchpad: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
| tags: | added: information-type |
| visibility: | private → public |
To post a comment you must log in.
Fixed in stable r15324 <http://