Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate SEV rating from ACTION reported #255

Open
AevaOnline opened this issue Oct 16, 2019 · 1 comment
Open

Separate SEV rating from ACTION reported #255

AevaOnline opened this issue Oct 16, 2019 · 1 comment

Comments

@AevaOnline
Copy link

Is your feature request related to a problem? Please describe.

Severity levels are unique, and both reporter and moderator see the same severity rating on an event.

As a moderator, this forces me to either:

  • rank "actions" arbitrarily in a linear-increasing order of "severity"
  • only create one entry per "rank" of "action"
    which results in highly reductive entries available to my community on the "consequence" form.

It also forces the reporter and moderator to use the same numerical rating to represent the perceived severity of the event. Experience tells me this isn't how humans triage situations. The "category" and "severity" of something are best identified separately.

Desired solution

Allow a project admin to configure multiple items with the same SEV rating, and allow a reporter to indicate the type of "Action" separately from the perceived "severity" of the incident.

Eg, "inappropriate speech on a chat channel" could be a very low-severity incident, or a very high severity; it depends on the context, who the involved parties are, and what was said.

Additional context

I realize this approach of "it's all relative - and perspective matters" is more difficult to put into code, or to build a linear process around, but I believe it's important to allow for that subjectivity. A reporting system like Beacon needs to represent simultaneous-and-different perspectives on the same event.

@CoralineAda
Copy link
Contributor

I'm thinking of dropping the severity levels altogether. Originally the concept was a "consequence ladder" (borrowed from Mozilla) with escalating levels of severity, which made sense. But since changing the concept to more of a action/consequence, the severity levels don't seem to make as much sense (and, as you noted, are highly contextual).

My thinking based on your comments is that there are actions/consequences, and severity levels, and they are not related to each other. Severity levels are only visible to moderators, or are done away with entirely (looking for your thoughts here).

The second purpose of the levels has to do with the order of their display (again, increasing in impact from minor to major). I'm thinking a drag-and-drop ordering would serve the purpose better.

Let me know what you think and I'll work on implementation this coming week. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants