T47230, T91868, and T232432 are duplicates or related.

Not sure how this should be fixed. We can just use a LogFormatter to change the link dynamically and not change what is inserted into the database (the "@global" thing). Or we may change the target to Special:CentralAuth/$name (and dynamically fix links in the old entries using the LogFormatter) and make this consistent with global rename logs (as mentioned in some of the other tasks), but this breaks consistency with older entries and makes searching less intuitive.

Perhaps we should add a hook to the core that would allow extensions to eavesdrop on the target input field on Special:Log and possibly add more (log_namespace, log_title) pairs for searching. (I don't think we can use log_search for this.)

In T139495#7549709, @matej_suchanek wrote:

We can just use a LogFormatter to change the link dynamically and not change what is inserted into the database (the "@global" thing).

I think this would be best. I wouldn't want to break power-users search workflow, or sub-page links to Special:Log, or bots or whatever else may depend on the current parameters. The format may be weird, but it seems unhelpful to change it now after almost 20 years.