Failing watches should have a "reschedule" button

Bug #558415 reported by Graham Binns
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Graham Binns

Bug Description

For watches which have failed less than (arbitrarily) three times in the last 5 attempts (i.e. are succeeding 60% of the time), we should provide a button to reschedule the watch for "now". This will set the next_check time of the watch to datetime.now() so that it gets checked in the next checkwatches run.

Related branches

Graham Binns (gmb)
Changed in malone:
status: Triaged → In Progress
Graham Binns (gmb)
Changed in malone:
status: In Progress → Fix Committed
milestone: none → 10.04
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
Changed in malone:
assignee: nobody → Graham Binns (gmb)
tags: added: qa-needstesting
Graham Binns (gmb)
tags: added: qa-bad
removed: qa-needstesting
Changed in malone:
status: Fix Committed → In Progress
Revision history for this message
Graham Binns (gmb) wrote :

Marked this as qa-bad since next_check is settable by launchpad.Admin only, though any user can see the button.

The fix for this is to make rescheduling go via a setNextCheck() method on BugWatch, which checks that next_check is settable using the functionality currently residing in BugWatchActivityPortletView.userCanReschedule().

Revision history for this message
Ursula Junque (ursinha) wrote :
Changed in malone:
status: In Progress → Fix Committed
tags: added: qa-needstesting
removed: qa-bad
Graham Binns (gmb)
tags: added: qa-ok
removed: qa-needstesting
Graham Binns (gmb)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.