Firefox/Input/Feedback to Bug
Feedback to Bug
Summary
Sometimes users leave feedback on Input that describes a particular bug and is detailed enough to serve as the basis for a Bugzilla bug. We want Input analyzers to be able to click a button on the feedback response view that opens up Bugzilla with a bunch of fields pre-filled with data from the feedback response.
Status
- Project owner: None
- Status: Planning
History
- 2011: Tell Us More project is created to supplement the sad feedback form with an option for users to file Bugzilla bugs directly.
- December, 2015: Osmose is briefed on the project at Mozlando.
- December 18th, 2015: Osmose writes this intiial project plan.
Phase 1
Summary
This phase will be the bare essentials for testing out the feature, showing it on all feedback pages and being as dumb as possible about filling in the Bugzilla form fields.
Requirements
- Add a "File a Bug" button to the feedback response view that:
- Opens up Bugzilla in a new tab with the fields pre-filled out based on the feedback.
- Determines the correct product/component based on the Product the feedback was left in.
Input to Bugzilla Mapping
Input Field | Bugzilla Field |
---|---|
Feedback | Summary |
URL | URL |
Technical Info | Link in Summary? See also? |
Email address | None (we're supposed to keep these private!) |
Measuring success
If we use a custom event in GA for when users click the file a bug button, we should be able to compare button clicks to views of the feedback page to measure engagement.
Question: Is the button being used?
This is measured by:
clicked on the file a bug button -------------------------------- total views of the feedback page
Our expectation is that the button won't be used very often, so we're not entirely sure what a goal is here. However, Phase 1 is low enough effort that measuring isn't too critical.
Bugs
Main bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1233866
Future phases
Future phases will be figured out after the most recent phase is completed so we have time to act on what we've learned.
Future phases may include:
- Adding a new listing of feedback that shows feedback that are considered likely good bugs.
- Searching bugzilla for bugs related to the feedback response.
- Automatically generate the bug instead of pre-filling out the form.