Firefox/Features/about-crashes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Make crash reports helpful and easier to access
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Definition
| style="font-weight: bold; background: #DDD;" | Status
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | ETA
|Feature status note=Waiting for UX input.
| style="font-weight: bold; background: #DDD;" | Owner
}}
|-
{{FeatureTeam
<section begin="status" />
|Feature product manager=Asa Dotzler
| [[Firefox/Features/about-crashes|Make crash reports helpful and easier to access]]
|Feature feature manager=Sheila Mooney
| {{StatusHealthy|status=Early planning}}
|Feature lead engineer=Blair McBride
| TBA
|Feature qa lead=Vlad Ghetiu (irc: vladg)
| Sheila Mooney
|Feature ux lead=Alex Limi
<section end="status" />
}}
|-
{{FeaturePageBody
|}
|Feature overview=Improve about:crashes to be more helpful and easier to access crash reports.
|Feature users and 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)


== Summary ==
==== Technical user / Developer ====
Improve about:crashes to be more helpful and easier to access crash reports.
* Gather more information when its needed to debug the crash
 
|Feature non-goals=* Will not change the way crash reports are gathered/submitted.
== Team ==
* Is not a replacement for crash-stats.
* '''Feature Manager''': Sheila Mooney
* Will not provide all information that crash-stats provides.
* '''Lead Developer''': Blair McBride
|Feature functional spec===== Additional information to expose ====
* '''Product Manager''': Sheila Mooney
* '''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 ==
Vaguely related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=336872
 
Related project: https://addons.mozilla.org/en-US/firefox/addon/crash-report-helper/
Related project: https://wiki.mozilla.org/PostCrash
 
== Designs ==
Waiting for UX input.
 
=== Additional information to expose ===
* Date/time of crash
* Date/time of crash
* Related SUMO articles
* Related SUMO articles
Line 58: Line 38:
* Crash signature
* Crash signature


=== Notes ===
==== Notes ====
* Group by date range?
* Group by date range?
** Makes it easier to see time-based trends
** Makes it easier to see time-based trends
Line 64: Line 44:
** Obscure way to expose whether something is submitted already, or will be submitted by clicking link
** 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. [[User:Jesse|Jesse]] 04:32, 21 April 2011 (PDT)
** 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. [[User:Jesse|Jesse]] 04:32, 21 April 2011 (PDT)
|Feature implementation notes=Vaguely related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=336872


== Test Plans ==
Related project: https://addons.mozilla.org/en-US/firefox/addon/crash-report-helper/
TBA.


== Goals/Use Cases ==
Related project: https://wiki.mozilla.org/PostCrash
=== Average user ===
}}
* Get links to recent crash report(s) for SUMO
{{FeatureInfo
** Submit first, if necessary
|Feature priority=P3
* Tell SUMO how often a crash is occuring
|Feature roadmap=User Support
* Disable add-on suspected of causing crash (assuming it hasn't been blocklisted)
|Feature list=Desktop
 
|Feature engineering team=Desktop front-end
=== Technical user / Developer ===
}}
* Gather more information when its needed to debug the crash
{{FeatureTeamStatus}}
 
== 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.
 
 
__NOTOC__
 
[[Category:Features]]
[[Category:Firefox]]
[[Category:Priority 3]]

Latest revision as of 19:40, 29 July 2011

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.

{{#set:Feature name=Make crash reports helpful and easier to access

|Feature stage=Definition |Feature status=` |Feature version=` |Feature health=OK |Feature 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 `

{{#set:Feature product manager=Asa Dotzler

|Feature feature manager=Sheila Mooney |Feature lead engineer=Blair McBride |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Vlad Ghetiu (irc: vladg) |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature 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

Vaguely related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=336872

Related project: https://addons.mozilla.org/en-US/firefox/addon/crash-report-helper/

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

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |Feature overview=Improve about:crashes to be more helpful and easier to access crash reports. |Feature users and 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

|Feature dependencies=` |Feature requirements=` |Feature 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.

|Feature functional spec===== 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)

|Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=Vaguely related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=336872

Related project: https://addons.mozilla.org/en-US/firefox/addon/crash-report-helper/

Related project: https://wiki.mozilla.org/PostCrash |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=P3

|Feature rank=999 |Feature theme=` |Feature roadmap=User Support |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=Desktop front-end }}

Team status notes

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

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}


Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/Features/about-crashes&oldid=334716"