We'd like to rewrite a page in Socorro using React to test out whether we want to extend this to the rest of the site. I've chosen the crash detail page due to it's lack of complex widgets compared to other pages. Along with re-implementing the page itself, we want to write a set of automated frontend tests to cover the basic functionality of the page.

Commits pushed to master at https://github.com/mozilla-services/socorro https://github.com/mozilla-services/socorro/commit/9ca1407c23bbb7c16a503fd54e50fa6accb1969c Bug 1468810: Add scaffolding for development of React-based report index. https://github.com/mozilla-services/socorro/commit/6c6523e3a733d2854d23fcdeb4591aad428d2218 Merge pull request #4494 from Osmose/reports-frontend-initial Bug 1468810: Add scaffolding for development of React-based report index.

I'm going to go through and close all the related bugs and centralize the notes here. bug 1475072 - add "reprocess" tab The current implementation currently uses a script (reprocessing.js) to do the reprocessing and update the page. This should be remade to use React components. bug 1475046 - add "metadata" tab The tab would need the following data about the crash: - the description of the value and the value for each of the results of RawCrash().get(<crash_id>).keys() RawCrash is a class in socorro/webapp-django/crashstats/crashstats/views.py This is how the data could be obtained through an API: GET https://crash-stats.mozilla.com/api/report/index/<crash id>/metadata bug 1475050 - add "bugzilla" tab The tab would need the following data about the crash: - list of links to report this bug in Bugzilla for different products (e.g. Firefox, Core, External Software Affecting, Firefox, Toolkit) - a list of associated bugs in Bugzilla including: - a link of the bug - summary of the bug This is how the data could be obtained through an API: GET https://crash-stats.mozilla.com/api/report/index/<crash id>/bugzilla bug 1475055 - add "modules" tab The tab would need the following data about the crash from the a parsed_dump of the crash: - for each module of the parsed_dump: - Filename (missing_symbols, symbol_url, and filename) - Version (version) - Debug Identifier (debug_id) - Debug Filename (debug_file) - certification information - Signer (cert_subject) This is how the data could be obtained through an API: GET https://crash-stats.mozilla.com/api/report/index/<crash id>/modules bug 1475059 - add "raw dump" tab The tab would need the following data - the raw stackwalker output of the crash - whether the user has permissions to view raw dumps - links to view - raw dumps in various formats (e.g. .dmp, .json) - unredacted crash This is how the data could be obtained through an API: GET https://crash-stats.mozilla.com/api/report/index/<crash id>/modules bug 1475063 - add "extensions" tab The tab would need the following data about the installed extensions for the crash: - extension name - extension id - version - whether the extension is current This is how the data could be obtained through an API: GET https://crash-stats.mozilla.com/api/report/index/<crash id>/extensions bug 1475064 - add "telemetry" tab The tab would need the following data about the crash: - the TelemetryEnvironment from RawCrash().get(<crash_id>) as a JSON object RawCrash is a class in socorro/webapp-django/crashstats/crashstats/views.py This is how the data could be obtained through an API: GET https://crash-stats.mozilla.com/api/report/index/<crash id>/telemetry bug 1475070 - add "correlations" tab The current implementation currently uses a script (correlation.js) to add the correlation data. This should be remade to use React components.

We're not going forward with the react cupcake, so I'm closing out related bugs as WONTFIX.