It should be possible for an admin to disable bugtrackers that are behaving badly
Bug #225829 reported by
Graham Binns
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Graham Binns |
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://
This would be an admin-only function, but a useful one.
This would also go some way towards fixing bug 138949.
Changed in malone: | |
status: | New → Confirmed |
Changed in malone: | |
milestone: | none → 2.1.11 |
status: | Confirmed → In Progress |
Changed in malone: | |
milestone: | 2.1.11 → 2.1.12 |
Changed in malone: | |
status: | In Progress → Triaged |
milestone: | 2.1.12 → none |
Changed in malone: | |
status: | Triaged → In Progress |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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).