Page MenuHomePhabricator

Show the global block log on Special:CentralAuth
Closed, ResolvedPublic1 Estimated Story PointsFeature

Description

Feature summary (what you would like to be able to do and where):

Show the global block log on Special:CentralAuth - equivalent to the Previous global account changes (centralauth-admin-logsnippet) section for locks.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

  • Feature parity with global locks

Benefits (why should this be implemented?):

  • Easily review all prior global (b)lock logs in one central location

Notes:

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Anyone willing to work on this? The global block:yes is quite easy to overlook when looking at a centralauth page, showing log entries would greatly help that

Anyone willing to work on this? The global block:yes is quite easy to overlook when looking at a centralauth page, showing log entries would greatly help that

Would it be okay from your point of view to place the GlobalBlocking logs into the "Previous global account changes" section on Special:CentralAuth? If so, then it shouldn't be too hard to implement this and I should be able to make a quick change for that.

Adding a new section would also be possible, but it might need to be passed by design first just to check where the section would go on the page. Therefore, it might not be possible for Trust and Safety Product Team to do that as product/design is busy with other temporary accounts related work.

As far as THIS ask goes, I think that would be fine.

Likely should be a different feature request, but having having styling (or even just a class or id applied that could be targeted with css to highlight/etc) if there is a "YES" on these lines could also be helpful:

Locked: yes
Globally blocked: yes (block)

Likely should be a different feature request, but having having styling (or even just a class or id applied that could be targeted with css to highlight/etc) if there is a "YES" on these lines could also be helpful:

Locked: yes
Globally blocked: yes (block)

Yeah, I would suggest making a new feature request. Personally, I'd only support adding the CSS class so that users can modify the styling using their user CSS. Highlighting it for everyone might be confusing if the user isn't looking for that information when they visit Special:CentralAuth.

Given that in T358979#10115411 we said we would add this and that this change is small in scope, I can make a patch now for this.

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

[mediawiki/extensions/CentralAuth@master] Show GlobalBlocking blocks and unblocks logs on Special:CentralAuth

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

Change #1114009 merged by jenkins-bot:

[mediawiki/extensions/CentralAuth@master] Show GlobalBlocking blocks and unblocks logs on Special:CentralAuth

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

Suggested QA steps:

  1. Create an account (or find an account) that you can globally block
  2. Globally block, modify the global block, and globally unblock the account from step 1
  3. Open Special:CentralAuth for the username you were blocking and check that all the global block logs are shown. This should exclude any local disabling of the global block though.
Djackson-ctr subscribed.

QA is completed, I have verified the new code has been implemented and is functioning as expected (Previous Global Account Changes section will display the global block logs when a username is globally blocked/global block has been modified/global block has been removed... Also Local Disabling of the Global Block will not be listed in the Previous Global Account Changes section.

image.png (262×1 px, 63 KB)