Closed Bug 1338835 Opened 8 years ago Closed 8 years ago

Disable ability to flag vetted kb articles as abuse

Categories

(support.mozilla.org - Lithium :: Contributor and Question Forums, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: philipp, Assigned: guigs)

References

Details

Attachments

(1 file)

There is a steady stream of new non-valid abuse reports coming by people (randomly?) flagging kb articles as abuse - those are outnumbering real/actionable reports at the moment and wasting moderator time, so we should probably look into disabling this ability for reviewed kb content.
(from comment #1) > People are flagging individual KB article comments as abuse, not the entire article. Sorry, my mistake. You can also flag the entire KB article as abuse by using the Options menu at the very top of the article. That option should definitely be disabled.
NI Rachel,& Joni With a some of these KB articles getting hundreds of abuse reports it swamps the moderation abuse reports and makes it impossible to effectively review the genuine reports. Perhaps this could be assigned to one of you or someone else and prioritised. It will also need moving if it is not immediately resolved as it is currently in the old migration component.
Flags: needinfo?(rmcguigan)
Flags: needinfo?(jsavage)
In triaging process. Champion will update on priority.
Component: Lithium Migration → Contributor and Question Forums
Product: support.mozilla.org → support.mozilla.org - Lithium
QA Contact: nobody
NI'ing Roland to file a support case for this since I don't see a way for us to change it myself.
Flags: needinfo?(jsavage) → needinfo?(rtanglao)
See also bug 1354505 comment 9 and attachment 8858461 [details]. "Mark As Spam" is another option that should be disabled for published KB articles since it makes the article inaccessible.
joni can now file support cases (in fact any sumo employee can as of April) so i am needinfo'ing her (also i don't remember what was decided).
Flags: needinfo?(rtanglao) → needinfo?(jsavage)
:guigs please triage this bug (I think you have triaged it but forgot to set the priority) and leave a comment when you have done so
I asked the lithium community to see if anyone might have a solution for the two use cases for Abuse reports: https://community.lithium.com/t5/Strategy/Disabling-Abuse-Reports-on-TKB-Only/td-p/305844
Flags: needinfo?(rmcguigan)
I've submitted a new support case: https://supportcases.lithium.com/500610000061BMr
Flags: needinfo?(jsavage)
No longer blocks: 1348889
See Also: 13376691354505
Joni, Should you take this as assignee because you have filed the lithium case. The bug is currently not assigned. As far as I know we now never assign sumo bugs to Lithium. Or more likely it should be assigned to Rachel because of the component set by Madalina.
Flags: needinfo?(rmcguigan)
Flags: needinfo?(jsavage)
Flags: needinfo?(rmcguigan)
Assignee: nobody → rmcguigan
Marking INVALID. We aren't moving back to Lithium - see https://blog.mozilla.org/sumo/2017/06/28/important-platform-update/
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Flags: needinfo?(jsavage)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: