| Feature | Status | ETA | Owner |
| Make crash reports helpful and easier to access | Early planning | TBA | Jay Sullivan |
Summary
Improve about:crashes to be more helpful and easier to access crash reports.
Team
- Feature Manager: Jay Sullivan
- Lead Developer: Blair McBride
- Product Manager: Jay Sullivan
- QA: TBA
- UX: Alexander Limi
Release Requirements
TBA.
Next Steps
- Get someone from QA on board
- Flesh out a spec, including usecases, and what additional information to expose
- Design how to expose that additional information
Open Issues
TBA.
Related Bugs & Dependencies
None yet.
Designs
Waiting for UX input.
Additional information to expose
- Date/time of crash
- Related SUMO articles
- Related bugs
- Whether it's been submitted or not (currently hidden in the obscure format of the ID)
- User comment
- Whether we (Mozilla) want additional information to help diagnose the crash
- Whether it's known/suspected to be caused by a certain addon
- Include a button to disable that addon
Potentially useful info for technical users (toggle-able via hidden pref?):
- Crash signature
Notes
- Group by date range?
- Makes it easier to see time-based trends
- Remove usage of "bp-" syntax
- Obscure way to expose whether something is submitted already, or will be submitted by clicking link
Test Plans
TBA.
Goals/Use Cases
Average user
- Get links to recent crash report(s) for SUMO
- Submit first, if necessary
- Tell SUMO how often a crash is occuring
- Disable add-on suspected of causing crash (assuming it hasn't been blocklisted)
Technical user / Developer
- Gather more information when its needed to debug the crash
Non-Goals
- Will not change the way crash reports are gathered/submitted.
- Is not a replacement for crash-stats.
- Will not provide all information that crash-stats provides.
Other Documentation
TBA.