Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Charles Marcus wrote:
On 2010-11-11 9:47 AM, Rainer Bielefeld wrote:
the current bug tracking system is sufficien for expert communication,
but if masses of users will file their problems, we will loose overview,
soon. There are too less sort criterias for subcomponents, OS-Versions,
LibO version and and and, afaik we don't have an useful permissions
management ... . I'm afraid we will run into problems. Is there any
discussion concerning solutions for these problems?

'Masses of users' will not know how to properly report bugs.

As I have advocated in the past (on this and the OOo list), I would
suggest a two-tiered system - a simple bug reporting page for end users,
where they can report bugs, document format/compatibility problems and
feature requests. This page should simply require a validly formatted
email address, and should not require the user to create an account or
'log in' to anything.

This page should also be as simple as possible - ie, make it very easy
to pick one of the two main categories (Bug or Feature Request), and if
it is a bug, is it a document format/compatibility problem or 'Other'
(description). For the former, provide a simple way to upload the
document exhibiting the problem (after a prominent warning about
removing confidential information of course).

Volunteers would then manage these reports, verifying them, checking for
duplicate/existing bugs, asking for additional info from the reporter if
needed, etc - then, only once a bug has been verified, it would be
entered into the real bug tracker by the volunteer, who would make sure
it got reported correctly. If it is a complex feature request, the
volunteer could enter it into whatever 'Idea Discussion' system is
implemented, which would then also automatically open a corresponding
bug for tracking purposes. The system should also capture the reporters
email address when it is initially reported, and if/when the volunteer
enters the actual bug, the system should automatically generate an email
to the OP thanking them for their contribution and include a link to the
final bug report so the OP can track its progress if desired.
For years I have been saying exactly this. OOo has a bug reporting system that is TOTALLY WORTHLESS for ordinary end users, they will simply give up in frustration and stop using the software, going back to MS Office. The way of solving this problem as described above is exactly what I have always thought that should be done your certainly have my +1 here!

--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.