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

Prioritization of Issues at triage time #715

Closed
karlcow opened this issue Sep 30, 2015 · 8 comments
Closed

Prioritization of Issues at triage time #715

karlcow opened this issue Sep 30, 2015 · 8 comments

Comments

@karlcow
Copy link
Member

karlcow commented Sep 30, 2015

See Meeting

  • lack of priority, severity, site ranking. We like the idea of adding prioritization at the triage level.
    Probably with UI and cute icons. @calexity @magsout
    Need to work out how it should work.
@hallvors
Copy link
Contributor

We were joking about labels 'severity-sucks', 'severity-bad', 'severity-catastrophic' - I think those are pretty good actually, although in the UI we could have icons for them. I think personally it should not be just at "triage time" but also exposed to bug reporters - it would be interesting to see how reporters classify issues.

I also suggest adding a feature that can order a bug list by the Alexa rank (or similar ranking system) of the reported websites.

@adamopenweb
Copy link
Collaborator

@karlcow After speaking with @miketaylr, he suggested we try to sort this out soon. With the reports coming from SoftVision now, there will be many bugs that should have different priorities. Here's an example of a real bug, that probably isn't the highest priority to us.

I'm sure you'll have some suggestions as to how we could do this.

As for the labels themselves, it might make sense to replicate the scale on Bugzilla: P1 to P5. Though I don't think we need to use all 5 groups.

In fact it would be nice if regular priority simply didn't have a label.

@karlcow karlcow added this to the Labels Work milestone Mar 8, 2017
@karlcow
Copy link
Member Author

karlcow commented Mar 8, 2017

and this is very close to what #1413 is aka labels for work status. This one here is another category. I have the feeling we are starting to reach the point of a giant workflow graph to understand better what we need, do and how we solve it.

Also, maybe we need to think about all this meta-information in terms of work and UI and less in terms of labels. "when all you have is a hammer everything looks like a nail" and I have the feeling it's what we are doing with our GitHub hammer and our need for UI.

@karlcow
Copy link
Member Author

karlcow commented Mar 8, 2017

@miketaylr just gave me the https://github.com/servo/servo/labels as a counter-example. Indeed not bad.

@karlcow
Copy link
Member Author

karlcow commented Mar 9, 2017

Just putting it here for remembering
http://imgur.com/a/ZueSo

capture d ecran 2017-03-09 a 13 06 22
capture d ecran 2017-03-09 a 13 12 05

@softvision-sergiulogigan
Copy link
Collaborator

I also support the use of Priority and/or Severity codes. We can use either a L-M-H Severity scale (Low-Medium-High), a Severity 1-5 or Priority 1-5 scale.

@miketaylr
Copy link
Member

@adamopenweb and @karlcow will discuss how to move forward this week.

@karlcow
Copy link
Member Author

karlcow commented May 11, 2017

So during the meeting this week we discussed about prioritization.

The resolution has been to have

  1. to have ONE label for priority.
  2. to have the label set during the triage.

We need to iron some details. See #1554

I'm closing this.

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

No branches or pull requests

5 participants