Steve Edmonds schrieb:
Also that link suggests discussing the bug in users list for confirmation.
that might be some misunderstanding. Discussion in mailing list is
- there is a well founded suspect that there is no bug, but some
user error or LibO maloperation
- the reporter has problems to use bugzilla
- the reporter hass problems with English language.
It would be useful if the procedure for bug confirmation could be listed
clearly. Looking at the bugs it is not clear how a bug is moved from NEW
to UNCONFIRMED to CONFIRMED.
May be you can modify and improve the Wiki text to avoid such
That's a misunderstanding. NEW does not mean "New Report", but "New
confirmed Bug, has to be fixed":
So the normal order is UNCONFIRMED -> NEW (what means "Confirmed")
Unfortunately Bugzilla's default status is NEW, not UNCONFIRMED, and it
seems there is no way to modify that with the current Bugzilla version.
Unfortunately there is no way NEW -> Unconfirmed for too rare or not
reproducible bug reports. If I can't confirm such a "wrong NEW" report I
add UNCONFIRMED to Whiteboard and NEEDINFO to Keywords:
Thank you for your contributions, two-man rule is very useful to prevent
us from wasting developer manpower.
If you can confirm observation and think that all important information
is included into the report, you should change status to NEW (or delete
"UNCONFIRMED" from Whiteboard and "NEEDINFO" from keyword.
Unsubscribe instructions: E-mail to email@example.com
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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