Created page with "{{TopMenu/ja}} {{Menu/ja}} {{Menu.QA/ja}} {{Lang|バグ報告の詳細}}
{{TopMenu/ja}}
{{Menu/ja}}
{{Menu.QA/ja}}
{{Lang|バグ報告の詳細}}
以下のヒントは、''Bugzilla''でのさまざまな選択と入力枠の正しい利用に役立つでしょう。また、[[BugReport|バグ報告]]のヒントに触れてください!
Feedback'''''.
-->
あなたは'''''[http://libreoffice.org/get-help/bug/ バグ提出アシスタント]'''''を試してみたいですか？
LibreOfficeのメニュー'''''[ヘルプ] -> [フィードバックを送る]'''''から出来ます。
* バグ報告を行いたい場合、最初にBugzillaで適切なコンポーネント以下のサブコンポーネントをクリックして検索します。おそらくあなたの問題はすでに報告されているでしょう。ツールチップは、リンクの機能を区別するのに役立ちます。
** '''ⓘ''' 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, maybe you can add useful information from your investigations?
==選択ガイド==
===バージョン===
The Version picker should show the LibreOffice version where the problem appeared, this information should help to find the code change what causes the problem. 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 and modify the version picker if necessary.
**If you find out that the problem did not exist in more early LibreOffice versions (or in OOo 3.3) set ''regression'' Keyword.
** Same if bibisecting shows that the problem has been introduced in a version before the Version you find in the selector; please adjust the shown version after your tests.
:
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 [http://www.libreoffice.org/download here].
*For reports concerning '''''LibreOffice Portable''''' please proceed in the same way. If the problem only can be observed with a portable LibreOffice, please start Summary Line with "
[Portable]
" together with Release ''Version'' from Version Picker!
* For Dev-Builds see [[#Version_Picker:_Particular_Versions|Particular Versions]]
* For bugs '''''inherited from OOo''''' use most early available LibO version ''LibO 3.3.0 Beta2''
==== 新バージョン 2012-06-20 ====
The contents in the seelctor will be modified so that in future the Versions shown in the picker will be more similar to the Version shown in LibreOffice menu ''Help/About''. After Discussion on libreoffice-qa we have a decision, so it will look for new Versions:
{| class="wikitable sortable"
! scope="col" | Help / About
! scope="col" | Bugzilla Picker
! scope="col" | Info
! scope="col" | Remark''
|-
| 3.8.0.0.alpha0+
| 3.8.0.0.alpha0+ Master
| Master
|-
| 3.8.0.0.alpha1
| 3.8.0.0.alpha1
|
|
|-
| 3.8.0.0.alpha1+
| 3.8.0.0.alpha1+
| daily
|
|-
| 3.8.0.0.alpha2
| 3.8.0.0.alpha2
|
|
|-
| 3.8.0.0.alpha2+
| 3.8.0.0.alpha2+
| daily
|
|-
| 3.8.0.0.beta1
| 3.8.0.0.beta1
|
|-
| 3.8.0.0.beta1+
| 3.8.0.0.beta1+
| daily
|
|-
| 3.8.0.0.beta2
| 3.8.0.0.beta2
|
|
|-
| 3.8.0.0.beta2+
| 3.8.0.0.beta2+
| daily
|
|-
| 3.8.0.1
| 3.8.0.1 rc
| Release Candidate
|
|-
| 3.8.0.2
| 3.8.0.2 rc
| Release Candidate
|
|-
| 3.8.0.3
| 3.8.0.3 rc
| Release Candidate
|
|-
| 3.8.0.3
| 3.8.0.3 release
| Release, Final Version
| Bugzilla version renamed from ''3.8.0.3 rc''
|}
* There will be some further fine tuning concerning ''Daily Builds'' after ''alpha1'', this concept produces too many Versions for nearby 0 reports. But these are small details, 3.6.0.0beta2 will be the first Build following that scheme.
* Old Versions until LibO 3.5 only will loose the leading ''LibO '' in the picker
* There is no need for any manual changes, existing bugs will get their new Version automatically without any noise.
* The only restriction will be that in the afternoon the [[Bug Submission Assistant]] will not work for a short while between changes in the Bugzilla Database and the Update of the Assistant
===コンポーネント(component)===
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. The madeup words (blends) for the '''sub components''' should help to distinguish these sub components from other meanings of the words in it. Examples: ''FILEOPEN''
''OPEN Office XML'', ''SLIDESHOW''
"drag and drop SLIDE will SHOW ugly artifacts".
{{BugzAssHlp contrib}}[[BugzAssHlp_contrib_long|Read more ... >]]
==== フィルターとストレージ(filters and storage) ====
Import and export code, and I/O infrastructure shared between applications. Modules such as
{{FdoSCS2|filters%20and%20storage|package}}
{{FdoSCS2|filters%20and%20storage|sot}}
{{FdoSCS2|filters%20and%20storage|filter}} (please addname of filter like ''SVG'' or similar in Bugzilla Subject Line) and {{FdoSCS2|filters%20and%20storage|}} for anything else related. Mostly interesting for '''developers'''
==== フレームワーク(framework) ====
The application [http://en.wikipedia.org/wiki/Software_framework framework], ie. code shared between applications not part of the graphical toolkit pieces:
{{FdoSCS2|framework|framework}}
{{FdoSCS2|framework|desktop}} What used to be the desktop in StarOffice 5 - now the binary.
{{FdoSCS2|framework|sfx2}}: This is the gui code, much of which is now deprecated.
{{FdoSCS2|framework|}} for anything else ''framework'' related
==== graphics stack ====
The VCL toolkit, drawing layer, and all non-print specific rendering functionality, interesting for '''developers'''{{FdoSCS2|graphics%20stack|}}
==== sdk ====
The UNO runtime environment, UNO API and SDK, interesting for '''developers'''{{FdoSCS2|sdk|}}
{{BugzAssHlp BASIC}}[[BugzAssHlp_BASIC_long|Read more ... >]]
{{BugzAssHlp Chart}}[[BugzAssHlp_Chart_long|Read more ... >]]
{{BugzAssHlp Database}}[[BugzAssHlp_Database_long|Read more ... >]]
{{BugzAssHlp Documentation}}[[BugzAssHlp_Documentation_long|Read more ... >]]
{{BugzAssHlp Drawing}}[[BugzAssHlp_Drawing_long|Read more ... >]]
{{BugzAssHlp Extensions}}[[BugzAssHlp_Extensions_long|Read more ... >]]
{{BugzAssHlp Formula Editor}}[[BugzAssHlp_Formula_Editor_long|Read more ... >]]
{{BugzAssHlp Installation}}[[BugzAssHlp_Installation_long|Read more ... >]]
====Libreoffice====
If you can't find any other appropriate component:
{{FdoSCS2|Libreoffice|MinGW}} for ''MinGW'' problems,
{{FdoSCS2|Libreoffice|}} for all other issues.
====言語(Linguistic)====
Formerly ''Linguistic component'', renamed 2012-05-17
For problems with
{{FdoSCS2|Linguistic|SPELL}} (check),
{{FdoSCS2|Linguistic|HYPHENATION}},
{{FdoSCS2|Linguistic|RTL}},
{{FdoSCS2|Linguistic|THESAURUS}}. Please do not use this component if your problem only affects a particular language.
{{FdoSCS2|Linguistic|}} 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.
{{FdoSCS2|Localization|UI}} for User Interface problems (bad translations ...), {{FdoSCS2|Localization|}} for all other problems!
{{BugzAssHlp Printing and PDF export}}[[BugzAssHlp_Printing_and_PDF_export_long|Read 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:
{{FdoSCS2|Presentation|CONFIGURATION}},
{{FdoSCS2|Presentation|EDITING}},
{{FdoSCS2|Presentation|FILEOPEN}},
{{FdoSCS2|Presentation|FILESAVE}},
{{FdoSCS2|Presentation|FORMATTING}},
{{FdoSCS2|Presentation|PDF}},
{{FdoSCS2|Presentation|PRINTING}},
{{FdoSCS2|Presentation|SLIDESHOW}} for problems with running presentation,
{{FdoSCS2|Presentation|RTL}},
{{FdoSCS2|Presentation|UI}},
{{FdoSCS2|Presentation|VIEWING}},
{{FdoSCS2|Presentation|odf_validation}} (temporary for [[Impress Documents ODF validation]]),
{{FdoSCS2|Presentation|}} 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:
{{FdoSCS2|Spreadsheet|CONFIGURATION}},
{{FdoSCS2|Spreadsheet|EDITING}},
{{FdoSCS2|Spreadsheet|FILEOPEN}},
{{FdoSCS2|Spreadsheet|FILESAVE}},
{{FdoSCS2|Spreadsheet|FILTER}},
{{FdoSCS2|Spreadsheet|FORMCONTROLS}},
{{FdoSCS2|Spreadsheet|FORMATTING}},
{{FdoSCS2|Spreadsheet|PIVOTTABLE}},
{{FdoSCS2|Spreadsheet|PDF}},
{{FdoSCS2|Spreadsheet|PRINTING}},
{{FdoSCS2|Spreadsheet|RTL}}
{{FdoSCS2|Spreadsheet|UI}},
{{FdoSCS2|Spreadsheet|VIEWING}},
{{FdoSCS2|Spreadsheet|}} for all other problems!
{{BugzAssHlp UI}}[[BugzAssHlp_UI_long|Read more ... >]]
{{BugzAssHlp Writer}}[[BugzAssHlp_Writer_long|Read more ... >]]
{{BugzAssHlp WWW}}[[BugzAssHlp_WWW_long|Read 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 q'''UI'''t ...")
* 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 ====
[[File:BzLifecycleold.png|right|300px]]You can find general information concerning bug fixing workflow and related Bug status [http://www.bugzilla.org/docs/3.6/en/html/lifecycle.html here].
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 [https://bugs.freedesktop.org/show_bug.cgi?id=31754 bug 31754], please see how much information has been gathered additionally to the original report.
Reports with status ''Unconfirmed'' will be checked by other users, if the problem is reproducible with a current version, considered as a real bug and description is complete 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. Should be used for existing bugs if more information is required from reporter or commenters before bug fixing can be started and before the Bug has been assigned. More details [[QA-FAQ#How_to_use_Status_or_Keyword_NEEDINFO|here]]!
===== バグを再オープンする方法(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 ====
* '''Master''':
** '''Master old -3.6''' is for all Bugs that have been observed in ''Daily Builds'' from a [http://dev-builds.libreoffice.org/daily/master MASTER] subdirectory until LibreOffice 3.6. Because of the very wide Range, especially for bugs observed in 3.5 Master (Summer 2011), the most early 3.5 released version where the problem also has been observed might be more useful, but a general recommendation is difficult.
** Starting with LibO 4.0 every Major Release will get it's own Master Version in Bugzilla (like '''4.0.0.0.alpha0+ Master ''')
* In Master Build Bug reports please always also mention [[Development/Tinderbox|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 '''[[QA-FAQ#MinGW|MinGW]]''' if a problem only can be observed in those Master builds
* '''3.4 Daily''' is for all Bugs that have been observed in ''LibO 3.4'' related ''Daily Builds''. These builds are no longer available.
* '''3.5 Daily''' is for all Bugs that have been observed in ''LibO 3.5'' related ''Daily Builds'' from [http://dev-builds.libreoffice.org/daily/libreoffice-3-5 libreoffice-3-5] subdirectory.
=== ホワイトボード(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:
* '''bibisected36older''' for a Bug what has not been observed in a late LibO 3.5 but appeared in all 3.6 Versions available for tester for bibisecting.
* '''bibisected35''', '''bibisected35older''' and '''bibisected35newer''' bibisected regression as per [[QA/HowToBibisect]].
** ''bibisected35'': this bug has been bisected in the range of [http://cgit.freedesktop.org/libreoffice/core/tag/?id=MELD_LIBREOFFICE_REPOS MELD_LIBREOFFICE_REPOS] and [http://cgit.freedesktop.org/libreoffice/core/tag/?id=libreoffice-3-5-branch-point libreoffice-3-5-branch-point] tags.
** ''bibisected35older'': the commit that introduces the bug is older than [http://cgit.freedesktop.org/libreoffice/core/tag/?id=MELD_LIBREOFFICE_REPOS MELD_LIBREOFFICE_REPOS] tag.
** ''bibisected35newer'': the commit that introduces the bug is newer than [http://cgit.freedesktop.org/libreoffice/core/tag/?id=libreoffice-3-5-branch-point libreoffice-3-5-branch-point] tag.
** You may add '''''bibisectrequest''''' if you can't do a Bibisect, but believe that that would be useful because the Bug has already been reproduced with Linux and probably appeared with a Version for what [[QA/HowToBibisect#Versions|Bibisect is available]]
** If you can do Bibisect and are willing to help to narrow down the Version where the bug appeared, you can use [https://bugs.freedesktop.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=PLEASETEST&chfieldfrom=-2d&chfieldto=Now&list_id=87479&product=LibreOffice&query_format=advanced&status_whiteboard=bibisectrequest&status_whiteboard_type=allwordssubstr&title=BibisectRequest%20Bug%20List&ctype=atom this] [http://en.wikipedia.org/wiki/Atom_Feed Atom Feed] to get message for new Bugs with Whiteboard entry ''bibisectrequest'' (what should be removed when you did the Bibisect).
::
* '''BSA''' means that this bug has been submitted using the [[BugReport#How_to_use_the_Bug_Submission_Assistant |'''B'''ug '''S'''ubmission '''A'''ssistant]]
*'''[https://bugs.freedesktop.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=numberformat&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_status=NEEDINFO&bug_status=PLEASETEST&component=Spreadsheet&product=LibreOffice numberformat]'''
: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 [[ReleasePlan|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 (or in a later stable Version) '''without a known fix''', a developer or QA member should change the Bug report Status to ''WORKSFORME'' with Whiteboard '''target entry in parenthesis''' with the first known version without the bug like "(target:4.0.0)". If the problem vanished in a Master version, 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''' for behavior which is evident only when the user has checked Tools > Options > LibreOffice > General > "Enable experimental (unstable) features".
* '''rtf_filter''': to distinguish general RTF related bugs form particular ones related to the ''new'' RTF import filter. This helps to track down those new filter related bugs more easily. Use of this key word needs detailed knowledge concerning new filter. Experts are Miklós Vajna, Lubos Lunak , Cédric Bosdonnant (for example).
* '''lhm-limux''': used to mark a bug as significant for the City of Munic Limux-project. Should be assigned only by members of the City of Munic, and is used to filter those bugs.
You can find additional key words for ''Whiteboard'' on [[Development/Easy Hacks Bugzilla Whiteboard Status]] and [[Design/Whiteboards/Color_Handling#Relevant_Bugs]]
=== 重要度(Severity) ===
Below is a general description of each level of severity from most severe (Blocker) to least severe (Enhancement). These are meant to be general guidelines for QA individuals trying to triage bugs. At the end of the section is a flowchart which provides an example of how one could potentially triage severity of bugs as they are moved from UNCONFIRMED to NEW or ASSIGNED. These are meant to be guidelines not strict standards, any suggestions to make the process better should be made through the QA mailing list where we can discuss potential changes.
* Blocker
:Bug so grave it should block the release; see our [[Release Criteria#Blocker_Bug_Definition|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 for Enhancement|vote process]]
====Example Flowchart(s)====
Feel free to amend this section with examples of how triaging severity can be done. There is no one right way but when it is being done the QA member should do everything in their power to be consistent. Also, try to comment when changing things so that other members and our users know your thought process.
[https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Example_1.jpg]
=== キーワード(Keywords) ===
* regression
:this worked in a previous release of LibreOffice, so the bug has been recently introduced.
* l10n
:localization issue (don't use i18n, use l10n)
* patch
:there is a patch attached to the issue
* security
:security related issue
* patcheswelcome
:bug/enhancement which has been closed due to lack of time/importance to implement but developers welcome to make a patch if they have the time or desire to do so.
=== 参照 ===
Here please Add Bug URLs to related Reports in
*[https://bugs.launchpad.net/ubuntu/+source/libreoffice Ubuntu tracker]
*[http://en.opensuse.org/openSUSE:Bugreport_LO#LibreOffice_Bug_Reports openSUSE tracker]
*[https://issues.apache.org/ooo/query.cgi AOOo Bugzilla Issue] for bugs with expected roots in old OOo code. Currently we have research for bugs ''[[User:RBd/Workbench#AOOo_Issues_From_Symphony|From Symphony]]''.
[[Category:JA]]
[[Category:QA]]