The mass block CheckUser interface should be split to a separate special page.
We could still display the form on the CheckUser results page, however, it would POST to a different special page.
The special page could then be enhanced to support further blocking options like T24120: Enhance Blocking and tagging from checkuser interface: add dropdowns.
Also, separating it from CU permissions would enable us to open it up to all administrators (and possibly move it out of CU?).
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T139810 RFC: Overhaul the CheckUser extension | |||
| Resolved | Dreamy_Jazz | T132892 CheckUser UI revamp | |||
| Resolved | Dreamy_Jazz | T69811 CheckUsers "Get users" design needs improvements | |||
| Resolved | Feature | Dreamy_Jazz | T24120 Enhance Blocking and tagging from checkuser interface: add dropdowns | ||
| Duplicate | None | T145340 Split CheckUser mass-block interface to separate special page |
Massblocking accounts seems like something conceptually unrelated to checkuser, so yeah moving it out of CU makes sense.