You must change the 'importance' from 'normal' to 'enhancement'.

well actually you are totally right: there is a missing bit on the homepage. I have put our website mailing list on CC as this can be easily changed for persons you do translate and edit the homepage...

I have to say that changing the 'importance' to 'enhancement' is totally wrong. It is just wrong on so many levels. This way of doing it is designed by a programmer, not by a user. Please, please make your bugzilla pages friendly to the ordinary mortal who writes for a living and who would never guess (and I didn't guess either) that you treat an enhancement like a bug all the way to deciding its importance. 
If you think that changing the 'importance' is actually a good idea, then I give up.Sorry.

Thanks for the very speedy response. I'm just so sorry that I can't congratulate you on the system's design. 

And another thing -- I had to choose what part of the whole of Libre Office I wanted to report a bug about. There was nothing in the combo box about 'Bug Reporting system'. Is this an oversight? Or is it bug free?

AFAIK, website-related issues should be filed at redmine.documentfoundation.org. The page should be updated to make it clear for once.

Created a Redmine ticket: https://redmine.documentfoundation.org/issues/1370

John: you are welcome to join the QA team. Hopping on IRC is a good start: http://webchat.freenode.net/?channels=libreoffice-qa

See also https://wiki.documentfoundation.org/QA

Hi, Beluga,

I visited the site redmine.documentfoundation.org suggested in Comment 5 and there is no obvious way to submit either issues or enhancement requests. it looks like it is only meant for people who already know what they're doing. Not for mere people like me.

Thanks for creating the ticket for me. It looks like your Bugzilla tool is really designed for people who can learn it. Users like me only want to use it one a year.

I am supported in my daily programming activities by small OCX suppliers (eg ciansoft.com) and major service providers (eg bulksms.com). None of them give me headaches when trying to report a bug. All of them communicate by e-mail. Quite probably the larger ones have a bugzilla to keep them organised, but only their support people get to use it.

An excellent example of how to handle enhancement requests is provided by bulksms.com's site. You write your idea on their site, they publish it and every visitor can vote for any enhancement request if they like the idea. Couldn't be simpler. And very democratic.

By the way, thanks for inviting me to join your QA team. However, I'm much better at designing for users than I am at making sure the product is stable and fits the spec. I clicked on the IRC link and it opened a web site asking me for my nickname. I don't actually have one. Maybe I'm too old to understand this urge to belong to social networks like IRC and Facebook. (I joined IBM as a trainee programmer 52 years ago).

I also had a look at the other place you suggested https://wiki.documentfoundation.org/QA. Now I  **know** that I'm right. If you need to have a web page explaining how to use the web page to report a bug then the whole system is too complicated for little people. I buy a package from ciansoft to control a scanner from inside my program and I get a problem. I em-mail the support@... web site. I get an e-mail back. Why should Libre Office be any different? I can infer that you are some sort of volunteer, core team member or whatever, and you trawl the new postings giving an initial response. That's exactly what I mean. The big difference is that you sent me an e-mail I'm not supposed to reply to (I did that once before and got told off). Then your e-mail includes a link to GodZilla so that I *must* use this horrible system. 

Anyway, thanks for the interest you have taken. Hopefully I won't find any bugs that I can't find a workaround to. When I designed a multi-user OS for a University 40 years ago I had to offer coffee vouchers to students who reported bugs. Otherwise they just found a workaround and the bug remained unresolved. This might happen to you if reporting bugs is too complicated.

Yes, we are all volunteers in the QA team. In addition, TDF employs a part-time QA engineer taking care of our self-hosted Bugzilla.

I will be the first to admit Bugzilla is not a prime example of user experience design. Yet, TDF does not have a bottomless chest of funds they could throw at upsteam improvements to Bugzilla. BZ is a Mozilla product, so any complaints should be primarily directed at them as they have orders of magnitude more funds.

To my knowledge BZ was already used before LibreOffice forked from OpenOffice. LibreOffice used the Bugzilla instance hosted at Freedesktop.org from 2010 to January 2015. This means we have had a relatively short time to make any tweaks of our own to the BZ. 

The QA team has its hands full dealing with the 600-800 monthly new reports. Having to learn Perl and the innards of Bugzilla on top of the usual bug-wrangling is not a very attractive idea for most members. We are of course expanding the team constantly and with any luck we might bump into some Perl-savvy person eager to contribute.

Another option, especially if we were to win the lottery suddenly, would be to explore more modern bug trackers & project management systems. Yet, they tend to fall short compared to BZ in other, more technical aspects (I'm thinking of Phabricator now in particular).

I understand your aversion to IRC, but I want to note it is 27 years old, predating WWW which we are using now to discuss :)
For an IRC nickname you can just make one up, no need to register or confirm anything beforehand.