Create a "Diagnose a bug" user story

[karlcow]

Currently "diagnose a bug" leads to bugsahoy with a few caveats.

• it doesn't contain all the open issues currently in web bugs.
• What does that mean to diagnose bugs. There is a missing context/guide for proceedings.
• layout.

So we might need a user story to tell us what we really mean by diagnose a bug.
It will help us open a couple of issues so we can create the sensible interaction for this section of the site.

[karlcow]

Added (by mike) for discussions to the 2014-04-29 meeting Agenda.

[calexity]

I've been thinking about the best way to help someone understand how to diagnose a bug. Here's what I have so far. There are a lot of UI possibilities, but more important is the workflow (quick and not overly hand-holdy, but helpful). Let me know if you have trouble seeing these sketches and I can brighten them or type it. cc @karlcow @miketaylr

[karlcow]

@calexity

1. Wonderful and beautiful sketches. Can we implement those ;)
2. yes. The user story is much better.

What's happening usually:

1. Someone reports a bug saying: "Hey that sucks. it is broken."
2. There is a need for someone to understand if the bug is temporary, if it's really a bug or a grumpy users.
3. So we need to diagnose:
   1. Is there a bug?
   2. Is the bug reproducible?
   3. Is the bug visible on other browsers?
   4. Analyze!

So when someone is pushing, "Diagnose", an experimented user could directly access to what s/he has to do, but for someone who is starting, there could be indeed some help. To test the UI, alexa, even before designing it, maybe you could do a role play with developers around you. Basically by you incarnating the UI and a developer trying to "use you". That will make maybe apparent what is missing. Hmm needs to record it, if you want to keep memory of things.

[calexity]

Thank you for the detailed explanation @karlcow

I can definitely test the UI. I may pick a direction and sketch it full size for getting feedback. Your advice is very helpful on that direction.

Also a note - we added #126 #169 #171 #172 #173 #176 as stories breaking this work up.

[calexity]

I'm going to close this one as per the above comment - it has been broken into smaller stories. Feel free to reopen if you disagree!

[miketaylr]

Nah, sounds great. 👍