This has been a pretty long standing issue so it's possible I missed a ticket talking about it, but: currently it is far, far too easy for someone to suppress a page creation or an edit while forgetting to also suppress an abusefilter log entry or the page creation log entry. I have had multiple instances where I've had to point out to very experienced oversighters that they didn't fully suppress something! That's really bad, and shouldn't ever happen.
Whenever a revdel or suppression is made of any of the following:
- A revision
- A page deletion
- A log entry (e.g., an AbuseFilter log entry or a page creation log entry)
Then the suppression UI should allow easily suppressing the corresponding entries that would contain the same information that you're suppressing. That is, if you suppress a revision then you should be able to easily suppress any abusefilter entries that were generated with respect to that revision. (And, ideally, any future abusefilter entries from the same page that contained the content of said edit could also be suppressed.) If you suppress an abusefilter log entry, you should be able to easily suppress the revision the entry is associated with.
There are obviously varying levels of complexity that this can quickly balloon too, so I would suggest that an MVP resolution of this would be to allow automatic/easy suppression of related entries when suppressing a revision or page deletion, as this is almost always the first item that gets revdel'd/suppressed.
This issue is related to, but in my opinion distinct from, T19053 and T22447.
See also: T44734: Non-admins can see contents of deleted pages when viewing abusefilter details
