Jump to content

QA/BSA/BugReport Details: Difference between revisions

From The Document Foundation Wiki
< QA | BSA
RBd (talk | contribs)
m fix typo in tag
(One intermediate revision by the same user not shown)
Line 171: Line 171:
** At the time of bug resolution, the developer should set the target marker to indicate to which version the bug fix will be applied (if it has not been already set).  
** At the time of bug resolution, the developer should set the target marker to indicate to which version the bug fix will be applied (if it has not been already set).  
** If a bug in a stable version vanished in the Master without a known fix, a developer or QA member should change the Bug report Status to ''WORKSFORME'' with Whiteboard entry with the Master version (September 2011: ''target:3.5.0''). In a comment the complete Master build ID what has been tested without seeing the bug should be mentioned. So other users seeing the problem during their tests can find out easily where they can await a version without the bug.
** If a bug in a stable version vanished in the Master without a known fix, a developer or QA member should change the Bug report Status to ''WORKSFORME'' with Whiteboard entry with the Master version (September 2011: ''target:3.5.0''). In a comment the complete Master build ID what has been tested without seeing the bug should be mentioned. So other users seeing the problem during their tests can find out easily where they can await a version without the bug.
* '''experimentalEnabled''', '''experimentalDisabled''' for behaviour which is evident or not depending on what the user has selected in Tools > Options > LibreOffice > General > "Enable experimental (unstable) features".





Revision as of 15:13, 13 March 2012

The following hints should help you to use the various Bugzilla selections and input panes in the correct way. Please also mention hints on BugReport!

May be you want to try new Bug Submission Assistant (currently experimental)
  • If you want to report a bug, first click the appropriate Subcomponent under the component (if already available, work in progress) to search Bugzilla, may be your problem has already been reported. Tooltips help to distinguish link-functions.
    • leads to Help for Subcomponents
    • If you did not find a bug report concerning your problem, click ► behind the Subcomponent to reach a prepared Submission page; you will have to complete the Subject line, select your OS and LibreOffice #Version and, of course, to add your report.
    • If you found a report concerning your problem, may be you can add useful information from your investigations?

Selection Guide

Version

Please use the Version picker to select the earliest LibreOffice version where the problem has been observed, especially for regressions it is important to have an indication with what version the problem appeared.

QA-Team members should try to find out during review whether also more early versions have been affected by the reported problem. If you find out that the problem did not exist in more early versions set regression Keyword.

If your LibO version is not available in Versions picker, please add information in Summary line like ''[OOO340m1 (Build:401)]'' or similar and use unspecified from Version Picker! You might find versions what do not yet exist, information concerning the latest version you can find here.

  • For reports concerning LibreOffice Portable please proceed in the same way. For the current versions LibreOffice Portable 3.3.4 or 'LibreOffice Portable 3.4.3 please start Summary Line with " [Portable 3.x.x]" together with unspecified from Version Picker!
  • For Dev-Builds see Particular Versions

Components

Please select an appropriate component for your report. When you find a problem please always check whether only the application where you found it is affected or whether it is a general problem for all (or at least several) LibreOffice applications.

BASIC

For all problems with LibreOffice Basic.

Applicable Subcomponents are: BASIC , IDE , Macros , and for all other problems [1] ,

Read more ... >

Chart

For all problems concerning Data Charts and Plots, used in Spreadsheet or other components

Read more ... >

contrib

Use this component if you want to contribute tools, templates or similar to LibreOffice.

Account Request if you need a developer account for code contribution,
[3] for all other problems

Read more ... >

Database

For all problems concerning database application If applicable, please use one of the following key words in the Summary for more detailed specification:


Read more ... >

Documentation

For problems with manuals, user guides and Help pages.

Applicable "sub-components" are: Drawing , Formula editor , Presentation , RTL , Spreadsheet , Writer .

For problems with the (built-in or online) Help pages LOCALHELP

Read more ... >

Drawing

For all problems concerning the DRAWING application for vector and bitmap drawings.


Read more ... >

Extensions

For all problems with Extensions. Applicable Subcomponents are:
Extensionname for Problems with a particular Extension (please replace Extensionname in the the Bugzilla Summary line by the name of the Extension, followed by the Extension version if applicable)

[6] for all other [ problems] with LibreOffice Extensions.

SI-GUI if you want to report problems with the Windows Server Installation Assistant Read more ... >

Formula Editor

For all problems concerning the formula editor.

Applicable Subcomponents are: EDITING , FILEOPEN , FILESAVE , FORMULAEDITOR (for experimental formula editor), FORMATTING , UI , VIEWING , [7] for all other problems.

Read more ... >

Installation

For all problems concerning installation or LibreOffice. Possible subcomponents are

CONFIGURATION (for example missing file type association),
UI (for damaged dialogs during the installation).
For missing or wrong Help please use Component Documentation!
[8] for all other problems, if none of the other "Subcomponents" seems appropriate.

Read more ... >

Libreoffice

If you can't find any other appropriate component:
MinGW for MinGW problems, [9] for all other issues.

Linguistic component

For problems with SPELL (check), HYPHENATION , RTL , THESAURUS . Please do not use this component if your problem only affects a particular language. [10] for all other problems!

Localisation

For all problems that are related to a particular Language version of LibreOffice. Alternatively you can use one of the other components and set the l10n keyword. [11] for all problems!

Template:BugzAssHlp PDF exportRead more ... >

Presentation

For all problems concerning the presentation application. If applicable, please use one of the following key words in the Summary for more detailed specification: CONFIGURATION , EDITING , FILEOPEN , FILESAVE , FORMATTING , PDF , PRINTING , SLIDESHOW for problems with running presentation, RTL , UI , VIEWING ,
[12] for all other problems!

Spreadsheet

For problems concerning the spreadsheet application. If applicable, please use one of the following key words in the Summary for more detailed specification: CONFIGURATION , EDITING , FILEOPEN , FILESAVE , FILTER , FORMCONTROLS , FORMATTING , PIVOTTABLE , PDF , PRINTING , RTL UI , VIEWING , [13] for all other problems!

UI

For problems concerning User Interface. You should also use this component if your problem affects more than 1 Application or if you can't decide what the correct component might be.

Applicable Subcomponents are: ACCESSIBILITY for Accessibility issues.
CONFIGURATION for problems with customization of LibO (Dialog out of access, ...)
ERRORMESSAGE for useless or broken or wrong error messages.
FILEOPEN , FILESAVE ,
RTL for Right To Left problems.
VIEWING if GUI elements are not shown correctly.
[14] for all other problems!

Read more ... >

Writer

For all problems concerning the Word Processor including HTML editor. If applicable, please use one of the following key words in the Summary for more detailed specification: CONFIGURATION , EDITING , FILEOPEN , FILESAVE , FORMATTING , FORMCONTROLS , MAILMERGE , TABLE , PDF , PRINTING , RTL , UI , VIEWING .
[15] for all other problems!

Template:BugzAssHlp WWWRead more ... >


General hints

Please don't mix up key words for Subject line from this page with the Keywords in Bugzilla selection.

Some hints how to use Subject Line Key Words:

  • upper case will be visible enough for most key words, square brackets only are useful if the key word can be confused with parts of a word ("... unable to qUIt ...")
  • Use 2 key maximum
  • Use key words exactly identical to the letter, but you may integrate them into the subject line sentence like"WIKIHELP [UI] not available in all Languages"

Initial state

In accordance to hints in FreeDesktop Bugzilla, please use UNCONFIRMED if you are not absolutely sure that you really found a general problem and that it's not limited to your PC, that it has not been already reported, that it's a real bug and not a feature, ...

You will have to make Advanced Fields visible to see the status picker. If you reach the bug submission page from This Wiki, UNCONFIRMED will be selected by default.

Please also decide for UNCONFIRMED if you only can report the effect without complete background information. It's really important to release developers from such basic research. So an overcautious UNCONFIRMED generally is better than an overhasty NEW.

A sample for a bug report that better should have had UNCONFIRMED as initial state is bug 31754, please see how much information has been gathered additionally to the original report.
Reports with status Unconfirmed will be checked by other reporters, if the problem is reproducible with a current version the status will be set to NEW.

If you can't reproduce a problem although you tested with an identical system configuration like the reporter and see a serious suspect that current Status NEW is incorrect (for example because there might be no real bug, but some user error), please leave a comment!

Status NEEDINFO

This status is not available for new bugs.

For existing bugs it should be used if more information is required from reporter or commenters before the Bug has been assigned. Using key word for this is deprecated since November 2011, because using of the Status has some advantage (can not be forgotten when assigning, ...)

How to reopen Bugs
  • If you do not have much experience in Bugzilla, please only write your suspect that the bug reappeared in a comment. Someone from QA or a developer will take care.
  • 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. 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).
  • 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!).

Version Picker: Particular Versions

  • LibO Master is for all Bugs that have been observed in Daily Builds from a MASTER subdirectory. In Master Build Bug reports please always also mention Tinderbox name and Time stamp from downloaded file. That will ease to find out whether a build used for review is more current or not compared to reporter's version.
    • Please always check whether the problem also can be observed in the current stable builds, use LibO Master only for problems only visible in Master versions.
    • Subject Line of the report should start with pseudo key word MinGW if a problem only can be observed in those Master builds
  • LibO 3.4 Daily is for all Bugs that have been observed in LibO 3.4 related Daily Builds from dev-builds.

Whiteboard

Here you can add some tags to make the bug easier to find for queries. Do NOT use it for random comments! Separate the tags you use in Whiteboard status by a whitespace, do not use commata. The one tag in Whiteboard status should never contain whitespace itself, use underscore instead (e.g. "data_loss"). Following standard phrases have been used frequently:

  • bibisected35, bibisected35older and bibisected35newer bibisected regression as per QA/HowToBibisect.
    • bibisected35: ???
    • bibisected35older: ???
    • bibisected35newer ???
Used by developers to identify bugs related to Calc's number format handling code.
  • perf
for performance issues
  • odf is a very general keyword for any kind of interoperability problem in consuming or producing ODF documents
  • odf_validation is specifically for bugs about LO producing invalid or non-conforming ODF documents
  • target:X.Y.Z for the next Release where the fix will be available (no Beta, RC, ...)
    • It must be target followed by a colon (:) then the version number. It must be one word without whitespace in order for it to be usable via regexp search.
    • A target marker should always be set by the developer working on the bug, never by the reporter.
    • At the time of bug resolution, the developer should set the target marker to indicate to which version the bug fix will be applied (if it has not been already set).
    • If a bug in a stable version vanished in the Master without a known fix, a developer or QA member should change the Bug report Status to WORKSFORME with Whiteboard entry with the Master version (September 2011: target:3.5.0). In a comment the complete Master build ID what has been tested without seeing the bug should be mentioned. So other users seeing the problem during their tests can find out easily where they can await a version without the bug.
  • experimentalEnabled, experimentalDisabled for behaviour which is evident or not depending on what the user has selected in Tools > Options > LibreOffice > General > "Enable experimental (unstable) features".


You can find additional key words for Whiteboard on Development/Easy Hacks Bugzilla Whiteboard Status

Severity

(to be more detailed.)

  • Blocker
Bug so grave it should block the release; see our Release Criteria
  • Critical
crashes, loss of data, severe memory leak
  • Major
major loss of function
  • Normal
regular issue, some loss of functionality under specific circumstances
  • Minor
minor loss of function, or other problem where easy workaround is present
  • Trivial
cosmetic problem like misspelled words or misaligned text
  • Enhancement
Request for enhancement
For Enhancements we have an experimental vote process

Keywords

  • regression
this worked in a previous release of LibreOffice, so the bug has been recently introduced.
  • l10n
localization issue (dont use i18n, use l10n)
  • patch
there is a patch attached to the issue
  • security
security related issue

See Also:

Here please Add Bug URLs to related Reports in