- #Worksforme bugzilla how to
- #Worksforme bugzilla free
Please note that all contributions to The Document Foundation Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 3.0 Unported License, unless otherwise specified. Based on work by Stéphane Guillou and Raal Raal and others. 
This page was last edited 18:55, 24 March 2023 by Ilmari Lauhakangas.
In any case please contribute a detailed step by step instruction how to reproduce your result that the problem has reappeared.
If the old bug is on Status WORKSFORME feel free to reopen after you checked carefully that you really observe the reported bug and whether your LibreOffice Version can contain the FIX therefore check the Whiteboard target information!). If you are not a very experienced user or if there is any little doubt, please submit a new bug report and mention your suspect in the report (citing old FIXED Bug number). For your tests please exactly reproduce the step by step instruction of the original report with the new LibO Version. If the bug is on Status FIXED, please check very carefully whether you really observe that the old bug reappeared (that happens really seldom) or whether you only observe very similar symptoms as mentioned in the FIXED bug. Someone from QA or a developer will take care. If you do not have much experience in Bugzilla, write in a comment that the bug still exists. This field is reserved for developer working in the bug. Please, do NOT assign the bug to the info provider. When you change Status to NEEDINFO please list info provider and missing information in your comment. Status NEEDINFO should be used if information in the report is not sufficient to start the bug fixing process. If you can't reproduce a problem, even though you tested with a system configuration identical to the reporter's, and you suspect that Status NEW is incorrect (for example because there might be no real bug, but some user error), leave a comment on the report. Attachments-in many cases attachments are needed to reproduce the problem if attachment(s) are not provided, this can hinder proper fixes. Steps to reproduce the problem-if not clear from summary and/or description. No duplicate can be found (bug has not been reported yet). Do not use this Status if you only do not understand the observed behavior NEW may not be used for LibreOffice 3.3.0 Bugs reproduced on 3.3.1 or similar 
The bug still exists for a current LibO version.NEW is for bugs that can be reproduced and still need a fix. UNCONFIRMED is for bugs that have not been reproduced by other users or on a different PC. Unfortunately, the explanations in Bugzilla are not for the existing bug Status items.
Every LibreOffice bug in Bugzilla has one of the following statuses:
0 kommentar(er)
