Hmm, this is already possible, at least for me locally?

@He7d3r: Is this a request for an "All (private and public) logs" item in the dropdown? Could you clarify?

I am seeing the same result as Florian on mediawiki.org.

Yes, that. From the description:

For convenience, all logs related to that page, that the user has the rights to see, should be displayed in the same list.

Ok, I think I now get the point, however, I probably just can't reproduce it. I created a page, TestIndex, and saved it. Then I created a new AbuseFilter, which prevents any edit (action = "edit"). I logged out and tried to edit the page "TestIndex", which was prevented by AbuseFilter. I then logged in again (as sysop) and looked at the pages history, clicked on "Show logs for this page" and the page navigated to Special:Logs with the page name as the target. Now, even if I select the AbuseFilter log, I can't see any log entry, as the target is not the page, which triggered the filter.

However, if I open "Special:Log" directly, I can see all log entries, even the ones from AbuseFilter, in one list, when I select the "All" logs option.

So, probably someone has to explain it to me. I really want to get this task fixed :)

Hello, I think the above comments conflate two issues.

Bug: Log names are not listed in the drop-down, and/or public logs are not invoked by "Show logs for this page".

Feature request: User should be able to view a combined feed across all namespaces including every log type for which they have permission (Aklapper's comment).

The latter would be startlingly helpful to admins on small public wikis, such as myself. At times I am the only active user besides bots and spammers, and I must refresh many logs again and again to stay current: is anyone hitting the edit filters? the blacklists? did someone else just checkuser this obstreperous account, therefore I need not do so per the privacy policy? The proposed change would condense eight tabs into one IIRC (even more the next time we upgrade MediaWiki).

I suppose the default display would stay unchanged for the benefit of WMF projects, where the typical human user is already overwhelmed by the high volume.

I realize this would take some effort per T21494 and others, because not all logs have identical database fields, but the above seems to make an obvious use case in every low-traffic installation lacking an ops staff (whose power users have never heard of Phabricator or development cycles). IOW the silent majority supports me 100%. :D

This appears to have been the case at one point, but the behaviour was changed in 2009 to only show private logs when specifically requested.

See 76b9c5d1d2c90995274b1803d2ced3cb453dc7b1 by @aaron

It should be fairly straightforward to revert that change, but I'd like to hear some support from the WMF/other developers before continuing. The current code is documented as only show [private logs] upon specific request to avoid suprises so it may be a good idea to continue supporting the all "public" logs at Special:Log, and have a separate way to request showing all public and private logs the user can see. Perhaps Special:Log/withprivate? or something?

Tagging CPT as a feature request to review

In T157218#6476509, @DannyS712 wrote:

The current code is documented as only show [private logs] upon specific request to avoid suprises so it may be a good idea to continue supporting the all "public" logs at Special:Log, and have a separate way to request showing all public and private logs the user can see. Perhaps Special:Log/withprivate? or something?

Was the idea to add an "all accessible logs" item in the dropdown dismissed already?