First change: on a stack signature summary report like http://crash-stats.mozilla.com/report/list?product=Firefox&query_search=signature&query_type=contains&range_unit=weeks&version=Firefox%3A3.0b5&signature=RtlEnterCriticalSection&range_value=1 we currently land on graph tab. we should land on the "reports" tab since that has the data that we are really after... we could also combine "graph" and "table" tabs if that makes life easier or faster. Second Change: on the individual crash report pages like: http://crash-stats.mozilla.com/report/index/6ac97075-04bb-11dd-b92b-001b78bc73ea we should land on the "frames" page. content from the "details" page could also be combined onto the top "frames" page to help put the stack trace into context.. when plowing though several hundred reports to chase down crashes these few changes would help to reduce a lot of clicks... setting to 0.6 since ted thought these would be easy... change the target milestone if not...
wwwwhhhhhaaa... no target milestone for this now... my hands start hurting everytime I spend any amount of time doing crash analysis.
We are re-triaging today. Morgamic is just resetting things in light of the php rewrite of the reporter.
Austin, could you see what's left to do here? Should be simple stuff.
WFM both items
landing on frames works for me too now, but on the first change I still get the graph page and not "reports"
I will make this change, so that query results page will display the list of crash reports, instead of the OS/Build graph. We are working on release currently and I will put it in.
These changes shipped. There is a regression of the frames tab, being tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=480501