[Bantracker] Add option to manually mark a ban as no-longer-set so that ops can clean out stale BT entries
Bug #1307768 reported by
rww
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu IRC Bots |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
There are a *lot* of stale (not actually set) #ubuntu Bantracker entries that can't be easily removed without causing a heck of a lot of spam in #ubuntu. A facility to manually mark them as no-longer-set would help to fix this. Using this facility should create a comment for tracking purposes, and there should probably be a facility to mark a ban as actually-still-set so that mistakes can be undone.
(This bug should be set to Wishlist. I'm going to pull the source and look at how hard it would be to do now.)
| description: | updated |
Revision history for this message
| rww (rww-deactivatedaccount) wrote | #1 |
Revision history for this message
| Terence Simpson (tsimpson) wrote | #2 |
| Changed in ubuntu-bots: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
To post a comment you must log in.
tsimpson let me know that this is implemented in the IRC interface as @clearban. That decreases my need for this web-side. I'll play with it and close this bug if it works fine for my use case.