Bug Q&A is one of the stories under development by the Launchpad Bugs team for what is being called Launchpad v4.0.

Contents

UDS Notes

What follows is the notes Deryck has from discussions at UDS (unedited, except for wiki-fying).

Bug prompts for triage help
- Based on triage state, or what's missing?
- if nothing but base bug, a generic "help triage" appears
- otherwise, prompts for specific missing info
Can you confirm this bug? (me too's, confirmed status)
- Why do we have a confirmed status? Do we need it still?
Steps to reproduce the bug?
- Add DB field for this (?)
- Update after description is updated and they confirm
Does this affect "PROJECT"?
- Need to get upstream link simpler and easier to expose, which makes this step nicer.
Custom questions supplied by PROJECT?
- Should not be subjective. yes/no
Can you fix this?
- Could assign to them (conflict ensues maybe)
Steps to fix (?)
Is there a branch? A patch?
Provide thanks feedback (and karma points added)
Bug rings (if you want to keep confirming)

(So Q&A box on page changes as you walk through these steps.)

Who do we prompt?
- (all users, certain users depending on state of triage)
- USER.is_bug_contributor vs. anyone ?
What does this look like on search page?
How does heat relate?

Outcomes

Plans

Goal: Make the smallest possible update to show where this is headed.

Integrate dialog into LP asking the first question
- "Can you confirm this bug?"
- Tick affected users, update links on page
- Dialog disappears (or moves to next question)
DB fields added, if needed
- flag for turning off Q&A dialogs ?
- a "steps to reproduce" field ?
- custom question machinary ?
Complete any remaining design questions
- i.e. be sure of the questions to add at this point