Page MenuHomePhabricator

[Epic] CheckUser 2.0: Preliminary check
Open, MediumPublic



Stewards and Checkusers sometimes need to decide whether a case warrants a check or not. For example, sometimes the user might just be new and unaware of the policies instead of being a deliberate sockpuppet. This can be judged by getting an overall picture of a user's accounts, contributions and some other information. We want to surface this information via a 'Preliminary check' tab in Special:CheckUser 2.0. The information on this tab should be the similar to what is present on Special:CentralAuth.
The preliminary check tab will only display public information and there is probably a future where this aggregated information will be integrated with Special:CentralAuth or there will be a way for non-CUs to access this. Because it is all public information, there will be nothing displayed if an IP address or a range is entered as in that case it would mean we tell the user about the users that have edited from those IPs. We could rethink this based on feedback. For the purposes of this ticket, the preliminary check only works for usernames.


Acceptance criteria

  • There is a preliminary check tab underneath the input form
  • Under the tab, there is a table with the headers:
    • Username
      • Usernames supplied in the input form
    • Registration date
      • Date-time on which the account was attached on the local wiki. This date is represented by the "Attached on" column in Special:CentralAuth
    • Wiki
      • Local wiki their account is attached on. Wiki name in canonical form like -, etc.
      • Note - There should be a 'home' icon next to their home wiki on the list. Special:CentralAuth denotes it in the Method column. For this user, meta wiki is their home wiki.
    • Contributions
      • Number of edits on that wiki which links to the contributions page on that wiki
    • Block status
      • Block status for the user with a link to the relevant block log (if possible)
    • User groups
      • This one is not in the mocks already - it displays any groups that the user is a part of on that wiki like admin, sysop etc displayed in a comma-separated fashion.
  • For each of the users entered in the input form, display all of the above information (following the mock structure)
  • There is a link to the Global contributions tool for each user under their username
  • Highlighting (This is still a WIP):
    • We want to highlight rows with similar fields when the user hovers (or have a way to sticky-highlight) over a cell in a row that is similar to another row's cell value. For this tab, the highlight would work for:
      • Date (note that the registration date is a date-time field but the highlight should work for the same dates - discarding the time value)
      • Wiki
    • Good to note that highlighting would also work for the compare tab, over fields like the date, IP, UA etc.

Related Objects

Open Prtksxna

Event Timeline

Niharika triaged this task as Medium priority.Oct 31 2019, 4:44 PM
Niharika created this task.
Niharika created this object in space Restricted Space.
Niharika renamed this task from CheckUser 2.0: Preliminary check to [Epic] CheckUser 2.0: Preliminary check.Nov 1 2019, 11:04 AM
Niharika added a project: Epic.
Niharika updated the task description. (Show Details)
Niharika shifted this object from the Restricted Space space to the S1 Public space.Nov 4 2019, 6:34 PM
Restricted Application added a subscriber: MGChecker. · View Herald TranscriptNov 4 2019, 6:34 PM
Huji added a subscriber: Huji.Nov 5 2019, 12:45 AM

Estimation meeting on Nov 5:

  • Decided on a limit of 2 users in the user input form for first iteration
  • Decided to work on the checkbox or including accounts using same IPs for later
  • Pagination can be a separate ticket
    • Question: Is pagination helpful after a point? Can we tell them if there are too many results and ask them to filter/narrow the results?
Niharika claimed this task.Nov 22 2019, 6:44 PM