Launchpad developers should be able to completely reset individual bug watches
Bug #624721 reported by
Graham Binns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Graham Binns | ||
Bug Description
We often get notifications about bug watch problems where the problems stem from something like this happening:
1. Bug watch update fails, error is recorded.
2. Bug watch is checked again.
3. Remote bug hasn't changed since last check, so checkwatches doesn't actually check it.
4. Error lingers forever.
Now, the correct way to fix the problem would be to fix checkwatches' behaviour for watches which have errored (bug 586754). Never the less, it would be nice to have a button on the BugWatch +edit page which allowed Launchpad developers and Admins to reset the watch completely (i.e. reset all its attributes to those it had when it was new). That would cause checkwatches to treat it like a brand new watch.
Related branches
lp://staging/~gmb/launchpad/lp-devs-can-reset-watches
- Abel Deuring (community): Approve (code)
-
Diff: 339 lines (+212/-3)8 files modifiedlib/canonical/launchpad/security.py (+11/-0)
lib/lp/bugs/browser/bugwatch.py (+17/-0)
lib/lp/bugs/configure.zcml (+5/-2)
lib/lp/bugs/interfaces/bugwatch.py (+11/-0)
lib/lp/bugs/model/bugwatch.py (+9/-0)
lib/lp/bugs/stories/bugwatches/xx-edit-bugwatch.txt (+67/-0)
lib/lp/bugs/templates/bugwatch-portlet-details.pt (+1/-1)
lib/lp/bugs/tests/test_bugwatch.py (+91/-0)
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote Bug fixed by a commit | #1 |
| Changed in malone: | |
| milestone: | none → 10.09 |
| tags: | added: qa-needstesting |
| Changed in malone: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r11462 <http://