Automatically hide reported resource when # of abuse reports exceeds a threshold
Problem to solve
Spam management is manually intensive and we should make monitoring easier. In https://gitlab.com/gitlab-org/gitlab-ce/issues/49808, we'd like to allow multiple reports on a single spam request. We should consider automatically hiding issues/snippets/comments/etc when we've received many reports on the same thing.
Proposal
- Define a spam report threshold.
- When an issue/snippet/comment/etc receives more reports than that integer, automatically hide it.
What does success look like, and how can we measure that?
TBD