Issue 33222 - RFE: provide a "file problem report" function [on the help menu]
Summary: RFE: provide a "file problem report" function [on the help menu]
Status: CONFIRMED
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: 680m49
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 53861 (view as issue list)
Depends on:
Blocks:
 
Reported: 2004-08-19 17:08 UTC by superbiskit
Modified: 2014-02-10 17:01 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description superbiskit 2004-08-19 17:08:28 UTC 
This Issue requests an item on the Help menu for "File Problem Report".
The function shall present an OOo form suitable for presenting input for
IssueZilla, upon completion the user shall be able to e-mail the completed form
to a robot at OpenOffice.org from which the appropriate issue shall be created.
Comment 1 stefan.baltzer 2004-08-30 11:58:02 UTC 
SBA: OOo already has an error report tool built in (automatically coming up once
an installation cashes). This is to "prove" that a crash really took place and
it eases fixing crashes that we are not able to reproduce.

If I get it right, this requests is for a button a button "I have a problem,
file a bug automaticcally" without requiring the user to log in to
Openoffice.org issue tracker.

Problem: 
"Automatically" always means "faster, easier but with less human influence or
control". In the crashreport tool, the default setting must be "Feedback = NO"
for privacy reasons. In many "non-crash" cases it is needed to contact the
reporter in order to track down a problem or clarify that it is yet again a
"How-Does-This-Work" case. And these are the most cases, far too often with the
justification "Different than Microsoft Office  => Must be a bug :-( - I don't
want such cases being reported automatically.

At times we have already far more _human-written_ issues than we can handle in a
reasonable time. Speeding up the amout of issues by easing their creation does
not look meaningful as long as the developers are as far from being bored as
they are right now. Only Reading and sorting a larger pile of issues (most of
wich will never get fixed but must wait for the respective area to undergo
changes) will even slow down the speed of fixing issues that must be fixed (say,
crashes :-).

I can imagine a button for the generation of mails describing a problem in
developer builds being meaningful. These could be collected on some kind of
newsgroup/mail alias, being sorted out by "skilled" QA folks and then being
processed. 

But who shall read them and "transform" them into "meaningful" issues? This must
be clarified before we enable "the world" to file issues of whatever "quality"
"with the click of a button". 

Reassigned to Bettina.
Comment 2 bettina.haberer 2010-05-21 14:59:26 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".
Comment 3 hanya 2014-02-10 17:01:39 UTC 
*** Issue 53861 has been marked as a duplicate of this issue. ***