Page MenuHomePhabricator

Add a check outcome feature
Open, MediumPublic

Description

When checking a user, we often check the log to see if anyone has recently checked the user.

Sometimes, we find that another checkuser has very recently checked the user, but not blocked them - we assume that nothing was found, and if needs be email the checkuser to confirm. Sometimes this can take a while.

I propose a "check outcome" which is logged against the check a la:

  • 15:08, 8 October 2017, There'sNoTime got edits for There'sNoTime (talk | contribs | block) (testing) (didn't find all the socks)

I imagine the flow would go something like:

  1. Check user (input check reason)
  2. View results
  3. Fill out check result (optional? required?)

Event Timeline

Special:Investigate, if the end button is added, could include this as the flow of checks is such that an end button is feasible. With Special:CheckUser, I'm not sure where you would put the result as each check result page would need to have a place to put the reason.

Change 884470 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/extensions/CheckUser@master] Add cul_result_id and cul_result_plaintext_id

https://gerrit.wikimedia.org/r/884470

Change 884470 abandoned by Dreamy Jazz:

[mediawiki/extensions/CheckUser@master] Add cul_result_id and cul_result_plaintext_id

Reason:

Will start from scratch.

https://gerrit.wikimedia.org/r/884470

Change 930944 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/extensions/CheckUser@master] Add cul_result_id and cul_result_plaintext_id

https://gerrit.wikimedia.org/r/930944

Change 930944 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] Add cul_result_id and cul_result_plaintext_id to cu_log

https://gerrit.wikimedia.org/r/930944

Change #1027557 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):

[mediawiki/extensions/CheckUser@master] Test SpecialCheckUserLog

https://gerrit.wikimedia.org/r/1027557