Launchpad itself

It should be possible for an admin to disable bugtrackers that are behaving badly

Bug #225829 reported by Graham Binns
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Graham Binns
Launchpad itself 2.2.3

Bug Description

At the moment, if a bugtracker that we're watching starts misbehaving (e.g. bug 175417) there's not much we can do about it except delete the bugtracker and all related bug watches.

However, what if it's something the size of the gnome-bugs bugtracker (http://launchpad.net/bugs/bugtrackers/gnome-bugs), which has 7000+ bug watches against it? We shouldn't just delete them, surely; we'd be better off being able to stop checkwatches from updating that bugtracker until it's been fixed (or we know where it has moved to or that we can definitely delete it).

This would be an admin-only function, but a useful one.

This would also go some way towards fixing bug 138949.

Diogo Matsubara (matsubara)
Changed in malone:
status: New → Confirmed
Revision history for this message
Graham Binns (gmb) wrote :

Another use-case for this would be private trackers. Someone may create a bug watch to a tracker that only they and their team have access to, but which Launchpad would not be able to get statuses from. Once Launchpad admins are aware of the situation they could disable the tracker to prevent it from spamming the checkwatches logs and OOPS report.

Bug 234254 has an example of this (I've deleted the watch but the link remains in the comments).

Graham Binns (gmb)
Changed in malone:
milestone: none → 2.1.11
status: Confirmed → In Progress
Björn Tillenius (bjornt)
Changed in malone:
milestone: 2.1.11 → 2.1.12
Graham Binns (gmb)
Changed in malone:
status: In Progress → Triaged
milestone: 2.1.12 → none
Revision history for this message
Graham Binns (gmb) wrote :

Assigning this to 2.2.2 as there's a lot of noise in the checkwatches report which could be reduced simply by not updating badly-behaved bug trackers.

Stopping those bug trackers from being updated is a relatively cheap fix.

Changed in malone:
assignee: nobody → gmb
importance: Undecided → Low
milestone: none → 2.2.2
Graham Binns (gmb)
Changed in malone:
status: Triaged → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote :

This has been marked in progress for over a month. Let's mark it Triaged until work on it begins again.

Changed in malone:
milestone: 2.2.2 → none
status: In Progress → Triaged
Revision history for this message
Graham Binns (gmb) wrote :

Targeting this to 2.2.3; it's more-or-less done bar the shouting.

Changed in malone:
milestone: none → 2.2.3
status: Triaged → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote : Bug fixed by a commit

Fixed in db r7817.

Changed in malone:
status: In Progress → Fix Committed
Björn Tillenius (bjornt)
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.
Subscribing...

Other bug subscribers

Remote bug watches

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