PostCrash: Difference between revisions

28 bytes removed ,  8 June 2010
Line 11: Line 11:
* the crash id
* the crash id
* the crash signature (source: Socorro)
* the crash signature (source: Socorro)
* associated bugzilla ids (source: Socorro) and status of these bugs (source: Bugzilla or Socorro)
* associated bugzilla ids (source: Socorro) and status of these bugs (source: Bugzilla or Socorro).
* if s crash is associated with a plugin, link to plugincheck (source: Socorro)
* If a bug is resolved fixed, show the version it was fixed in.
* if a crash is associated with a plugin, link to plugincheck (source: Socorro)
* If a canonical SUMO article exists, a link to that article, otherwise a link to SUMO search for that signature (as is currently done in Socorro)
* If a canonical SUMO article exists, a link to that article, otherwise a link to SUMO search for that signature (as is currently done in Socorro)


Line 25: Line 26:
* Search for a canonical SUMO article where one previously didn't exist
* Search for a canonical SUMO article where one previously didn't exist


In order to minimize load on Socorro and SUMO, we may only show this information for the last n crashes (where n is a smallish number, yet to be determined, perhaps even 1).  We could display a link to "check crash status" on each previous crash.
In order to minimize load on Socorro and SUMO, we will be default only show an expanded view for the most recent crash.  Users may individually expand other crashes (something like "check crash status" on each previous crash).
 
Question:
* Should we show both hangs and crashes?  Users may load the page and see  nothing but hangs. Does it make more sense to (perhaps by default) just show crashes?


== Changes to SUMO ==
== Changes to SUMO ==
* Add a table that stores links between articles and signatures.  The relationship may be m:n but is definitely 1:n. 
* Add a webservice call that, given a signature and locale, searches for relevant content on SUMO and returns a URI.
* Add a webservice call that searches for a canonical article and returns it if it exists.
* The web service should work as follows:
* Make the search accept OR searches, e.g. "crash_signature OR crashes", to ensure that generic crash support is shown even if there are no articles or forum threads mentioning the crash_signature.
**# If a canonical article exists for crash_signature (top search result), link directly to it, and display the title of the article
** Alternatively, make the webservice call above "clever", e.g.:
**# Else if search results exist for crash_signature, show search results
**# If canonical article exists for crash_signature, link directly to it
**# Else link directly to a single generic crash article
**# Else If search results exists for crash_signature, show search results
 
**# Else, link directly to generic crash article


== Changes to Socorro ==
== Changes to Socorro ==
1,107

edits