Ensure access when subscribing a user to a bug
Bug #1000045 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
When subscribing a user to a bug, unless they have been granted access to that bug, either via a policy grant or a direct artifact grant, they will not be able to see the bug or receive notifications. There are database triggers currently which ensure an access grant exists when subscribing. We want to remove these trigger and have the logic done in code.
Related branches
lp:~wallyworld/launchpad/subscribe-grants-access-1000045
- Curtis Hovey (community): Approve (code)
-
Diff: 463 lines (+273/-21)9 files modifiedconfigs/testrunner/launchpad-lazr.conf (+0/-15)
lib/lp/bugs/model/bug.py (+10/-0)
lib/lp/bugs/tests/test_bugvisibility.py (+22/-0)
lib/lp/registry/interfaces/accesspolicy.py (+1/-1)
lib/lp/registry/interfaces/sharingservice.py (+30/-0)
lib/lp/registry/services/sharingservice.py (+62/-4)
lib/lp/registry/services/tests/test_sharingservice.py (+135/-1)
lib/lp/services/features/flags.py (+7/-0)
lib/lp/testing/factory.py (+6/-0)
lp:~wallyworld/launchpad/createAccessGrants-robust
- William Grant: Approve (code)
- Diff: 0 lines
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: bad-commit-15359 qa-bad removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
| tags: | added: sharing |
To post a comment you must log in.
Fixed in stable r15359 <http://