Firefox/Features/about-crashes

Please use "Edit with form" above to edit this page.

Status

Make crash reports helpful and easier to access
Stage	Definition
Status	`
Release target	`
Health	OK
Status note	Waiting for UX input.

Team

Product manager	Asa Dotzler
Directly Responsible Individual	Sheila Mooney
Lead engineer	Blair McBride
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	Vlad Ghetiu (irc: vladg)
UX lead	Alex Limi
Product marketing lead	`
Operations lead	`
Additional members	`

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Improve about:crashes to be more helpful and easier to access crash reports.

2. Users & 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

3. Dependencies

`

4. Requirements

`

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.

Stage 2: Design

5. Functional specification

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
- Removing this will make pasting-into-Bugzilla fail :( We can de-emphasize the UUIDs, but when providing a list to paste, we should keep the prefix. Jesse 04:32, 21 April 2011 (PDT)

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

Related project: https://wiki.mozilla.org/PostCrash

Stage 5: Release

10. Landing criteria

`

Feature details

Priority	P3
Rank	999
Theme / Goal	`
Roadmap	User Support
Secondary roadmap	`
Feature list	Desktop
Project	`
Engineering team	Desktop front-end

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`