Bug 89321 - The (new) Document Foundation Bugzilla page needs to become more user oriented
Summary: The (new) Document Foundation Bugzilla page needs to become more user oriented
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-12 00:27 UTC by bugquestcontri
Modified: 2020-09-20 17:22 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugquestcontri 2015-02-12 00:27:39 UTC
I am sure the migration from the old to new Bugzilla site has a lost advantages in respect to analysis of the reports etc. I am also grateful to the people who work on this migration as volunteers. 

For the normal, not "IT fluent" LibO users, who use AskLibO for advice and/or simply want to report a report entry side (e.g https://bugs.documentfoundation.org//enter_bug.cgi?product=LibreOffice) is IMHO much too complex. 

Also I, being a bit more familiar with IT matters, I feel it this page is not clear and requires a lot of thinking on what needs to selected etc.

I will give only a few examples here but offer to discuss with people who are looking into the topic in more details

Component;
LibO has the components
Writer - listed OK
Calc - listed as Spreadsheet
Impress - listed as Presentation
Math - listed as Formula Editor
Base = listed as Database

in between there are many terms which are difficult to understand for normal LibO users.

Version
The default of "unspecifiied" I expect will be used often because it is not obivousl that scrollihg up is needed to find the currently actual versions of 4.2, 4.3, 4.4

Severity
Just because I know that there must be a possibility to flag a bug an enhancement request I searched and found "enhancement request" under Severity.


Enhancement could be done by 
1 - Using an interface page as it was used for a while with a clear differentiation between a bug report and an enhancement request
2 - Making this page a bit more understandable for normal LibO users.


As mention before already, I am willing to contribute with comments and solution ideas etc. I only cannot do some programming because I miss the knowledge for doing such work.

The Possible Dublicate Field is excellent and I hope it reduces a lot of work caused by multiple reports for the same bug.
Comment 1 A (Andy) 2015-02-12 18:24:12 UTC
I agree that some aspects can be improved.  

From my point of view most of the fields are necessary, but not the field "Hardware", because I think most users (that are no IT specialists) do not know what to select there.

I also agree that the naming in the "Component" field is not consistent as described by the Bug Reporter.  Maybe this list can also cleaned up or/and more information is provided to understand what is for instance ci-infra, contrib, framework, graphics stack, Linguistic, sdk, ux-advise?

Concerning the Enhancement issue I would also agree with the Bug Reporter.  I see again and again bug reports, where the user probably did not know that the differentation of a normal bug and an enhancement request can be found in the "Severity" field, because this is not intuitive.  This should be clearer.

The field "Version" is from my point of view ok.  I do not know if this can be further improved.
Comment 2 Robinson Tryon (qubit) 2015-02-12 18:43:13 UTC
Technically speaking, bugs about Bugzilla should go to Redmine:
https://redmine.documentfoundation.org/projects/infrastructure/issues/new

(In reply to A (Andy) from comment #1)
> to understand what is for instance ci-infra,

Yep, ci-infra should also migrate to Redmine, so that the 'LibreOffice' product can just focus on the LibreOffice suite (and nothing else).
Comment 3 BogdanB 2020-09-20 17:22:37 UTC
I think this bug should be close as mention in comment 2.
This is not the wright place to report that.