Issue 85588 - The error report response message should include the summary
Summary: The error report response message should include the summary
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: www (show other issues)
Version: current
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: troodon
QA Contact: issues@tools
URL:
Keywords:
: 89190 (view as issue list)
Depends on:
Blocks:
 
Reported: 2008-01-25 15:22 UTC by troodon
Modified: 2013-08-07 15:34 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description troodon 2008-01-25 15:22:31 UTC
Currently, when you send a crash report you get the following message by e-mail:

"Dear User,

Thank you for sending the error report generated by the OOo-dev error report
tool. Your error report has been received and will be evaluated. The ID of the
error report is xxxxxx.

Please do not reply to this automatically generated response.

Sincerely,
Your OOo-dev Team"

Since the automated responde includes the report ID but not the subject, there
is no obvius way of associating an ID with a report in case you've sent more
than one report in a short period of time.

So it should include the summary of the report too :-)
Comment 1 stx123 2008-01-28 12:28:47 UTC
moving to tools...
Comment 2 cno 2009-03-07 20:07:04 UTC
set to new
Comment 3 cno 2009-03-07 20:08:26 UTC
*** Issue 89190 has been marked as a duplicate of this issue. ***
Comment 4 cno 2009-03-07 20:10:06 UTC
Hi Bernd,
when in doubt, pls take time to read my last two comments with 89190. Thanks
Comment 5 epost 2009-03-09 14:54:14 UTC
CCed: jj
Comment 6 bernd.eilers 2009-03-09 15:22:06 UTC
working on it
Comment 7 bernd.eilers 2009-03-09 17:27:19 UTC
This has now been implemented.
Comment 8 cno 2009-03-09 17:36:11 UTC
thanks a lot :-)
Comment 9 bernd.eilers 2009-03-20 14:22:03 UTC
bei->	troodon: back to you for review and closing of issue.
Comment 10 troodon 2009-07-08 22:33:24 UTC
Confirming this is fixed. Thank you!