Merge lp:~danilo/launchpad/devel-bug-720826-clear-level-on-delete into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Данило Шеган |
Approved revision: | no longer in the source branch. |
Merged at revision: | 12504 |
Proposed branch: | lp:~danilo/launchpad/devel-bug-720826-clear-level-on-delete |
Merge into: | lp:launchpad |
Diff against target: |
48 lines (+9/-1) 3 files modified
lib/lp/bugs/interfaces/bugsubscriptionfilter.py (+1/-1) lib/lp/bugs/model/bugsubscriptionfilter.py (+4/-0) lib/lp/bugs/model/tests/test_bugsubscriptionfilter.py (+4/-0) |
To merge this branch: | bzr merge lp:~danilo/launchpad/devel-bug-720826-clear-level-on-delete |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Leonard Richardson (community) | Approve | ||
Review via email: mp+51768@code.launchpad.net |
Commit message
[r=leonardr][bug=720826][incr] Clear bug_notificatio
Description of the change
= Unset bug notification level on final filter removal =
== Background ==
For every structural subscription, we have recently started enforcing that there is at least one BugSubscription
As part of QA for
https:/
I realized that when trying to remove final subscription filter, we do not unset the bug_notificatio
This fixes that, and can be QAd in the same manner as the above MP.
== Tests ==
bin/test -cvvt test_delete_final
== Demo and Q/A ==
Add a structural subscription and go to https:/
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
This looks good.
Is there a better way to indicate that BugNotification Level.COMMENTS is the default value? That's the only problem I had reading this--it looked a little arbitrary.