QA/BSA/BugReport Details: Difference between revisions
No edit summary |
Add missing component for "Formulat editor" |
||
| Line 50: | Line 50: | ||
End Experimental | End Experimental | ||
<div class="component"> | |||
====Formula editor==== | ====Formula editor==== | ||
For all problems concerning the formula editor. If applicable, please use one of the following key words in the Summary for more detailed specification: | For all problems concerning the formula editor. If applicable, please use one of the following key words in the Summary for more detailed specification: | ||
Revision as of 14:50, 14 September 2011
TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate
We are just testing modified Templates, some functions might not work
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!
A new experimental template has been used for tests. Clicking on "Subcomponent" text will open a Bugzilla query for Writer + Subcomponent, clicking ► will open the Bugzilla submission input page for Writer + Subcomponent. ⓘ - Help for Subcomponents coming soon, first available is for VIEWING! Tooltips help to distinguish functions. May be you want to leave a comment on the Discussion page?
This page will become obsolete in December, because it is planned to enable a new Bug Submission Assistant
- 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.
- 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.
If your LibO version is not available in Versions picker, please add information in Summary line like ''[dev300m103]'' together with unspecified from Version Picker! You might find versions what do not yet exist, information concerning the latest version you can find here.
- For Missing 3.4.2 RC2 Please use [LibO 3.4.2 RC2] in Subject line (copy / paste from here)!
- For reports concerning LibreOffice Portable please proceed in the same way. For the current version LibreOffice Portable 3.3.0 please start Summary Line with " [Portable 3.3.0]" 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.
Experimental
BASIC
For all problems with LibreOffice Basic.
Chart
For all problems concerning Data Charts and Plots, used in Spreadsheet or other components
contrib
Use this component if you want to contribute tools, templates or similar to LibreOffice.
Database
For all problems concerning database application If applicable, please use one of the following key words in the Summary for more detailed specification:
- Status "ASSIGNED"
- Status "NEEDINFO"
- Status "NEW"
- Status "PLEASETEST"
- Status "REOPENED"
- Status "UNCONFIRMED"
- Status "VERIFIED"
Documentation
For problems with manuals, user guides and Help pages.
Drawing
For all problems concerning the DRAWING application for vector and bitmap drawings.
- Status "ASSIGNED"
- Status "NEEDINFO"
- Status "NEW"
- Status "PLEASETEST"
- Status "REOPENED"
- Status "UNCONFIRMED"
- Status "VERIFIED"
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
End Experimental
Formula editor
For all problems concerning the formula editor. If applicable, please use one of the following key words in the Summary for more detailed specification: EDITING ⓘ ►, FILEOPEN ⓘ ►, FILESAFE ⓘ ►, FORMULAEDITOR ⓘ ► (for experimental formula editor), FORMATTING ⓘ ►, UI ⓘ ►, VIEWING ⓘ ►. [7] ⓘ ► for all other problems.
Installation
For all problems concerning installation or LibreOffice. Use it if LibreOffice can't be installed of if your office suite will not work as expected after installation and there is a suspect that the problem is caused by a damaged installation. If the problem is only visible for a particular language version, pls. set the l10n keyword and add your localization in the beginning of the subject line (like [DE] for German). Possible subcomponents might be [8] ⓘ ► if none of the following "Subcomponents" seems appropriate, CONFIGURATION ⓘ ► (for example missing file type association), UI ⓘ ► (for damaged dialogs during the installation). For missing or wrong Help please use Component Documentation! [9] ⓘ ► for all other problems.
Linguistic component
For problems with SPELL ⓘ ► (check), HYPHENATION ⓘ ►and THESAURUS ⓘ ►. Please do not use this component if your problem only affects a particular language. [11] ⓘ ► for all other problems!
Localization
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. [12] ⓘ ► for all problems!
Experimental
Template:BugzAssHlp PDF export
End Experimental
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 ⓘ
►,
FILESAFE ⓘ
►,
FORMATTING ⓘ
►,
PDF ⓘ
►,
PRINTING ⓘ
►,
SLIDESHOW ⓘ
►,
UI ⓘ
►,
VIEWING ⓘ
►,
for problems with running presentation SLIDESHOW ⓘ
►,
[13] ⓘ
► 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 ⓘ ►, FILESAFE ⓘ ►, FORMCONTROLS ⓘ ►, FORMATTING ⓘ ►, PIVOTTABLE ⓘ ►, PDF ⓘ ►, PRINTING ⓘ ►, UI ⓘ ►, VIEWING ⓘ ►, [14] ⓘ ► 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. "Subcomponentw" (Subject Line key words can be:
CONFIGURATION ⓘ
► for problems with customization of LibO (Dialog out of access, ...)
ACCESSIBILITY ⓘ
► for Accessibility issues.
[15] ⓘ
► for all other problems!
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 ⓘ
►, FILESAFE ⓘ
►, FORMATTING ⓘ
►, FORMCONTROLS ⓘ
►, MAILMERGE ⓘ
►, TABLE ⓘ
►, PDF ⓘ
►, PRINTING ⓘ
►,
UI ⓘ
►, VIEWING ⓘ
►.
[16] ⓘ
► for all other problems!
Experimental
End Experimental
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 any 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, 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!
Version Picker: Particular Versions
- LibO Master is for all Bugs that have been observed in Daily Builds from MASTER subdirectory
- 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 leave a short temporary comment. Following standard phrases have been used frequently:
- CONFIRMED
- If you were able reproduce a problem and indicate it as a real bug. Please do not add the key word if further investigation will be required before the bug will be assigned to a developer. Currently no bulk change is planned, but if you find missing CONFIRMED or deprecated UNCONFIRMED while you are editing a bug report you should correct the Whiteboard field. This Whiteboard tag will no longer be required when "Bug 38425 - please use UNCONFIRMED as default initial state for new bugs for LibreOffice" will have been fixed.
- infoprovider:
- can be used together with Keyword field entry NEEDINFO. Insert phrase + user name or mail address of user who should contribute additional information
- Used by developers to identify bugs related to Calc's number format handling code.
- perf
- for performance issues
- RTL for all text direction Right To Left related
- target:X.Y.Z
- 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).
You can find additional key words for Whiteboard on Development/Easy Hacks Bugzilla Whiteboard Status
Severity
(to be more detailed.)
- Blocker
- Blocks development and/or testing work
- 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