You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
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:
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.
The text was updated successfully, but these errors were encountered: