Closed Bug 1299460 Opened 6 years ago Closed 4 years ago
Be more constructive in "Crash Not Found" error page
53 bytes, text/x-github-pull-request
|Details | Review|
After https://bugzilla.mozilla.org/show_bug.cgi?id=1262252 is done the logic for report index is simplified. If the raw crash doesn't exist in S3 we say "Crash Not Found". If the raw crash exists but the processed crash doesn't, we say "Processing crash now" (and behind the scenes the crash ID gets put in a priority queue). But what we could do is customize the "Crash Not Found" if the crash ID looks valid but implies a date that falls outside the current retention policy we have for saving raw crashes. This would help people who click on old links that once used to work but no longer does.
The text currently says: """ We couldn't find the Crash ID you're after. If you recently submitted this crash, it may still be in the queue. If you believe this message is an error, please submit a Bugzilla ticket describing what happened, and please include the URL for this page. """ We might want to adjust that text to help ease the issues in bug #1428517. cc:ing Guigs in case that helps her and the other support folk.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla-services/socorro https://github.com/mozilla-services/socorro/commit/30d724b491e9ae8441823c8bbcfc9d4e487c392c fix bug 1299460: improve crash not found page This improves the crash report not found page. It explains several reasons why the crash report may not be available and what to do about it. This includes the possibility that the crash report is no longer on our system. https://github.com/mozilla-services/socorro/commit/e6915afd89db56d19a37dfabbc3ef4a6200bef3f Merge pull request #4784 from willkg/1299460-no-crash fix bug 1299460: improve crash not found page
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.