Linking a private blueprint to a public bug/branch makes that artefact inaccessible
Bug #1130480 reported by
Steve Kowalik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Steve Kowalik |
Bug Description
Linking a private blueprint to a public bug results in a Forbidden message, whereas the blueprint should be hidden by those who can not know about it.
Related branches
lp:~stevenk/launchpad/filter-spec-lists
- William Grant: Approve (code)
-
Diff: 368 lines (+103/-41)11 files modifiedlib/lp/bugs/browser/bug.py (+5/-1)
lib/lp/bugs/interfaces/bug.py (+4/-2)
lib/lp/bugs/model/bug.py (+14/-5)
lib/lp/bugs/model/tests/test_bugtask.py (+33/-10)
lib/lp/bugs/templates/bug-portlet-specs.pt (+2/-2)
lib/lp/code/browser/branch.py (+6/-2)
lib/lp/code/browser/branchmergeproposal.py (+6/-3)
lib/lp/code/interfaces/branch.py (+4/-1)
lib/lp/code/model/branch.py (+22/-8)
lib/lp/code/model/tests/test_branch.py (+5/-5)
lib/lp/code/templates/branch-macros.pt (+2/-2)
tags: | added: 403 fallout |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Also affects public branches linked to private blueprints