@Albertoleoncio which wiki did you see this on and also has this recently changed?

We have recently made a large set of changes to Special:Investigate for T329189, so it would be useful to know whether this is related to that or was present before the changes that were recently made.

I looks like this behaviour is deliberate and was implemented before the changes in T329189.

The reason given for this in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CheckUser/+/602121 is that:

Since the results can't be sorted with an indexed query due to the way we aggregate them, they can't be sorted across pages. This means we can't make use of the TablePager's sorting infrastructure.

That means that the code that does sorting using the server was disabled but front-end sorting was enabled. However, the front-end sorting was only enabled when the results span one page. This seems to have been done to avoid confusion as the sorting feature on the table would only apply to that page of results, whereas normally the sorting applies to all pages of the results.

What it would be useful to know is whether you expect the sorting on the table to only apply to the specific page of results or all results.

Considering this isn't a bug per-se (because this was specifically intended in the patch that added the sorting), I am marking this as a feature request.

Em T366062#9837991, @Dreamy_Jazz escreveu:

Considering this isn't a bug per-se (because this was specifically intended in the patch that added the sorting), I am marking this as a feature request.

In other words, we have a classic case of "it's not a bug, it's a feature". hahaha.

I consider the lack of ordering to be particularly problematic, as it hinders one of the most essential functions of Special:Investigate, which is to help understand and organize complex sockpuppetry cases. Perhaps it is possible to imagine other solutions, such as increasing the number of lines per page, for example as it works with edit history of pages.