Details for Bug Reports

TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate

• Wiki Home
• Development
• Design
• QA
• Events
• Documentation
• Website
• Localization
• Accessibility
• Marketing
• Diversity
• Wiki Help

• Bug Report
• Bug Triage
• Projects
• Regression Test
• Automated Tests
• Bibisect
• QA Meetings
• QA FAQs

Attachments in general

It is almost always better to include an attachment with a bug report if at all possible, and if you can provide a relevant image or document. The attachment shows the bug-squishing team exactly what you, the bug reporter, are seeing or experiencing. A bug lacking an attachment can be (and usually is) placed into NEEDINFO status. Here are a couple of basic principles:

1. Simple Test Document
   1. Provide the simplest test document possible.
   2. Include what you wanted to do, the steps you took on the way to doing it, and where the thing happened that looks like a bug.
   3. If the test document is very long, or badly organized, it's much harder to dig through the content of the document to figure out exactly what's going wrong - it slows down QA, it slows down developers. A 100 page document with a bug report that says "go to page 3 and look at the third sentence" is not nearly as useful as a single page document that only has the third sentence in it.
2. Public
   1. Attachments are public, so do not post stuff the whole world should not be looking at. See the "Confidential Attachments" section.
3. Auto-Detect
   1. If you are reporting through bugzilla (https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&bug_status=UNCONFIRMED) and are attaching a document with the original report - please do the following:
      1. Select "Show Advanced Fields"
      2. Click "Add an Attachment"
      3. Select "auto-detect".

Confidential Attachments

LibreOffice generally does not accept confidential attachments. All attachments on our bug tracker are public and individual Quality Assurance members and Developers are typically unwilling to accept personal emails that contain confidential information. That being said, you can strip out the content by using the macros below:

Note: This only strips out content and is only tested with English locale.

Writer

1. Download template: https://wiki.documentfoundation.org/images/5/55/Confidential_Macro.ott
2. Enable Macros:
   1. Open LibreOffice
   2. Tools ▸ Options ▸ Security ▸ Macro Security...
      1. Set to Medium
3. Open downloaded file from file browser
   1. Select Enable Macros
4. Copy all content from confidential document into newly opened Untitled document
5. Run Macro
   1. Tools ▸ Macros ▸ Run Macro ▸ Expand (+ sign) Untitled, Standard
   2. Select Confidential
   3. Click Run
6. Save document as a new document name

All modules

You also can:

• Check Tools ▸ Options ▸ LibreOffice ▸ Security ▸ Options ▸ Remove personal information on saving
• Uncheck File ▸ Properties ▸ [General] ▸ Apply user Data, then
• Click Reset

More Information

• Sanitizing Files Before Submission