Closed Bug 1377632 Opened 4 years ago Closed 3 years ago
Write the crash-sig in the summary of an auto-generated crash-report in BMO with "@[ ]"
53 bytes, text/x-github-pull-request
|Details | Review|
Write the crash-signature in the summary-field of an auto-generated crash-report in BMO with "@[ ]". I think it's better readable and searchable in BMO. How it e.g. looks now: Crash in shutdownhang | vcruntime140.dll@0xc574 | huge_ralloc How it IMHO should looks like: Crash in [@ shutdownhang | vcruntime140.dll@0xc574 | huge_ralloc ] Steps to reproduce: - Open: https://crash-stats.mozilla.com/report/index/9cecca82-95de-4c69-b705-1fcad0170629 - Select under "Bugzilla - Report this bug in" the "Core"-component
I'd like to see some input from Product Integrity before I'd feel comfortable approving this change. It may impact other tooling or convention. If that happens and you want to change this, start here: https://github.com/mozilla-services/socorro/blob/master/webapp-django/crashstats/crashstats/templatetags/jinja_helpers.py#L225
I won't be able to work on this. This bug can be assigned to someone else.
Per Dipankar's request, I'm unassigning this. Further, this bug was created as a mentored bug, but there's no indication that Adrian offered to mentor it. He's been removing himself as mentor for other bugs, so I'm going to remove him as the mentor for this one, too. Adrian: If that's not ok, please re-add yourself. I don't see any urgency here and there are things to work out before any work on this should go forward, so I'm dropping this to a P5.
Assignee: cooldipanks14 → nobody
Status: ASSIGNED → NEW
Priority: -- → P5
Assignee: nobody → willkg
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.