Closed
Bug 869616
Opened 11 years ago
Closed 11 years ago
Crash reports with an email address should get a notification if that crash is believed fixed.
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mhoye, Unassigned)
References
(Blocks 1 open bug)
Details
As part of a larger evangelism goal, users that have provided an email address with their crash reports should get an email thanking them for their crash submission when the cause of the crash is believed to be fixed. That note should thank people for submitting that crash, and tell them that "we expect to make the fix for this crash available in Firefox [ver], available in [X weeks]. If you'd like an advance look at the next version of Firefox, join our Beta program! You can download Firefox Beta releases here! [url] The goals here are many, but a thank-you note for submitting a crash report and a confirmation that it wasn't a waste of time will go a long way, I think. Thanks, - mhoye
Comment 1•11 years ago
|
||
We're currently doing this. The current implementation kinda sucks, because we're emailing people repeatedly (once a week or so) if they submit multiple emails. I'd much rather cut back on the initial email and focus on emailing people when we 1) need more help 2) have solved the problem and want them to try it 3) know how they can fix their problem by upgrading something/uninstalling malware/etc. And of course we can't tell them that we expect the fix to be available in X unless we already know that ;-).
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Comment 2•11 years ago
|
||
If I want to contact everyone who reported (or reports) a given signature, how should I do that?
Comment 3•11 years ago
|
||
Jesse, right now email me and Cww. We'll help you decide which population you actually want to contact and whether it will actually help achieve you goals. Note that currently the messages cannot be localized, and so we're rather reluctant to do much more detailed emails until we've fixed that issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•