Page MenuHomePhabricator

Create support page for "Bullying" incident category
Closed, ResolvedPublic

Description

Requirements

User View

When a user selects the incident category "Bullying, intimidation, threats or repeated insults" and clicks Continue, the system must open a support page. The support page will contain the following sections:

  • Info header
  • "What to do next" section
  • "How to request help" section
  • "Can't find what you're looking for" section

Copy

Info header
Mandatory

  • Text: "Bullying, intimidation, threats or repeated insults. The information on this page is intended to help you resolve the incident."

"What to do next"

Mandatory:

Configurable through community config:

  • Links: "Dispute resolution" link is configurable

"How to request help"
Configurable through community config:
--Text (at least one option needs to be selected):

    • Contact an Admin for help with urgent or ongoing incidents on-wiki
    • Email your concern to [email@domain.com]
    • If you’re unsure what to do, ask the community for help
  • Links:
    • "Contact an Admin" link is configurable
    • Email is configurable
    • "ask the community for help" link is configurable

If no option is selected, this section will display the following default text:
" For issues that occur on-wiki it is recommended that you contact an admin or use a community noticeboard for help with urgent and ongoing incidents."

"Can't find what you're looking for?"
Mandatory

Community Config view

When an admin accesses community configuration, the following will be displayed:

Dispute resolution page (optional)

  • Text: "Add the link for a dispute resolution page"
  • Example text "e.g. Project:Dispute resolution"
  • Text: "This might be your local policy page"

"How to request help"

  • Text: " Add a least one contact method to display to the user"

Contact options

  • "Contact an Admin for help with urgent and ongoing incidents"
    • Text: "Add the link for the page that the user should go to "
    • Example text: "e.g. Project:Administrator's noticeboard"
  • "Email your concern, using a regular email address"
    • Text: "Add the email address that the user should email"
    • Example text: "e.g. incidents@wikimedia.org "
  • If you're unsure what to do, ask the community for help
    • Text: "Add the link for the page that the user should go to"
    • Example text: "e.g. Project:Village pump"

Designs

Proposed copy (WMF doc)
Figma file

Acceptance criteria

  • All the above are met

Event Timeline

Madalina updated the task description. (Show Details)

Let's drop the word "repeated". A user will be reporting a single comment, and it should suffice if they don't check whether the insult they see is one of many or not.

In fact, in UCoC the opposite reasoning is used: it's not an insult that's repeated. It's mockery, sarcasm, or aggression which, when interpreted collectively, may constitute insults, even if individual statements would not.

Change #1214108 had a related patch set uploaded (by STran; author: STran):

[mediawiki/extensions/ReportIncident@master] Add next steps page for non-emergency intimidation incidents

https://gerrit.wikimedia.org/r/1214108

Change #1214108 merged by jenkins-bot:

[mediawiki/extensions/ReportIncident@master] Add next steps page for non-emergency intimidation incidents

https://gerrit.wikimedia.org/r/1214108

image.png (278×683 px, 62 KB)

Findings

  • Icon does not match mockup
  • Spacing does not match design in attached screenshot. Also, it's inconsistent
  • Borders are not present, both on top and just before the button
  • [mobile web experience]"official policy" link: Screenshot shows a link that doesn't open in a new page. However, the implementation visually renders an external link that's expected to open in a new tab but it doesn't. Suggestion: target should be added to the <a /> element

image.png (2,186×110 px, 59 KB)

  • Primary button label. I just need clarity here. It doesn't match the mock but even with this approach, what happens when we have a long user name?
SectionCopy/ExperienceExpected copy/experience
Info header✅(per Figma)
"What to do next"Dispute resolution is often the first step for simple on-wiki issues.If you feel safe doing so, you can try talking to the person you are reporting on their user talk page. Remind them of the official policy and inform them that their behavior could lead to a temporary ban from editing.Dispute resolution is often the first step for simple on-wiki issues. If you feel safe doing so, you can try talking to the person you have concerns with on their user talk page. Remind them of the official policy and inform them that their behavior could lead to a temporary ban from editing.
"How to request help"
"Can't find what you're looking for?"

Change #1219181 had a related patch set uploaded (by STran; author: STran):

[mediawiki/extensions/ReportIncident@master] [WIP] Minor fixes to v2 non-emergency workflow

https://gerrit.wikimedia.org/r/1219181

Change #1219181 merged by jenkins-bot:

[mediawiki/extensions/ReportIncident@master] Minor fixes to v2 non-emergency workflow

https://gerrit.wikimedia.org/r/1219181

Team aligned that the copy difference isn't a blocker.