stub-in step 2. Pre-filter Bug Reports
← Older revision
Revision as of 2014-12-18T05:50:31
(One intermediate revision by the same user not shown)
Line 9:
Line 9:
== Where to Find Other QA Members ==
== Where to Find Other QA Members ==
There are a few places where you can find/contact members from the QA team, many of whom can help with triaging questions and are actively triaging themselves. <br />
There are a few places where you can find/contact members from the QA team, many of whom can help with triaging questions and are actively triaging themselves. <br />
−
1.
Mailing Lists
+
#
Mailing Lists
−
:
*libreoffice-qa@lists.freedesktop.org
+
#
*libreoffice-qa@lists.freedesktop.org
−
:
*libreoffice@lists.freedesktop.org
+
#
*libreoffice@lists.freedesktop.org
−
2.
IRC Channels on Freenode
+
#
IRC Channels on Freenode
−
:
* {{irc|libreoffice-qa}}
+
#
* {{irc|libreoffice-qa}}
−
:
* {{irc|libreoffice-dev}}
+
#
* {{irc|libreoffice-dev}}
−
+
#
QA Members<br>Here is a list of QA members (feel free to add your own name if you intend on contributing to QA). If the user has given you permission to contact them directly, feel free to do so. Also you'll find them hanging out in the chat rooms somewhat frequently.
−
3.
QA Members<br>
+
#
* [[QA/Team|QA Member List]]
−
Here is a list of QA members (feel free to add your own name if you intend on contributing to QA). If the user has given you permission to contact them directly, feel free to do so. Also you'll find them hanging out in the chat rooms somewhat frequently.
+
−
:
* [[QA/Team|QA Member List]]
+
== Steps to Triage a Bug ==
== Steps to Triage a Bug ==
Line 25:
Line 23:
==='''Summary of Steps'''===
==='''Summary of Steps'''===
# Find Bugs to Triage
# Find Bugs to Triage
+
# Pre-filter Bug Reports
# Search for Duplicates of Bug(s)
# Search for Duplicates of Bug(s)
# Check Information Provided in Bug Report
# Check Information Provided in Bug Report
Line 58:
Line 57:
* [https://bugs.libreoffice.org/buglist.cgi?list_id=8557&field0-0-0=creation_ts&query_format=advanced&bug_status=UNCONFIRMED&product=LibreOffice All Bugs that Need Triage Work]. (Limited to 500 bugs, full list will take some time to load as it's quite a long list - you can help to change that!)
* [https://bugs.libreoffice.org/buglist.cgi?list_id=8557&field0-0-0=creation_ts&query_format=advanced&bug_status=UNCONFIRMED&product=LibreOffice All Bugs that Need Triage Work]. (Limited to 500 bugs, full list will take some time to load as it's quite a long list - you can help to change that!)
−
* [https://bugs.libreoffice.org/buglist.cgi?list_id=114012&op_sys=Mac%20OS%20X%20%28All%29&query_format=advanced&bug_status=UNCONFIRMED&bug_status=REOPENED&product=LibreOffice All '''Mac OS X''' Bugs
, which needs
confirmation]
+
* [https://bugs.libreoffice.org/buglist.cgi?list_id=114012&op_sys=Mac%20OS%20X%20%28All%29&query_format=advanced&bug_status=UNCONFIRMED&bug_status=REOPENED&product=LibreOffice All '''Mac OS X''' Bugs
that need
confirmation]
−
====Step 2.
Search for Duplicates
====
+
====Step 2.
Pre-filter Bug Reports
====
−
Duplicates are bugs marked RESOLVED DUPLICATE which are very similar or identical but reported by different users.
+
−
Such bugs are automatically counted by Bugzilla and available at [https://bugs.libreoffice.org/duplicates.cgi?sortby=count&reverse=1&bug_id=46074%2C53006%2C46901%2C39007%2C38913%2C44664%2C50552%2C36263%2C53482%2C49853%2C46071%2C45081%2C44720%2C37488%2C37405%2C40298%2C43989%2C40571%2C46155%2C36301&sortvisible=0&product=LibreOffice&maxrows=50&changedsince=7 Most Frequently Reported Bugs] page. When triaging please check that list and do a quick search through bugs in Bugzilla to see if there are any duplicates of the bug that you have, but don't need to spend a lifetime on this. As you see more bugs you may remember seeing a similar bug and can easily close the newest of the two (or more) bugs. In general minimizing the amount of duplicate bugs entered into Bugzilla will save time for QA team members.
+
−
'''If you find a duplicate bug skip to step #5'''
+
Some bugs need special attention by specific teams:
−
====
Step 3. Check Information
====
+
====
= UX Enhancements =
====
−
Checking information is critical for development. What you should look for is the following:
+
Any bugs which cover enhancements
to the
UI
/
UX of LibreOffice should be given
to the
UX Team
−
# Clear and meaningful summary
+
−
# Clear problem description
+
−
# Steps
to
reproduce
the
problem -- if not clear from summary and
/
or description
+
−
# Attachments -- in many cases attachments are needed
to
reproduce
the
problem, if attachment(s) are not provided this can hinder proper fixes
+
−
'''If
all information is not properly there
,
skip to step
#
5
'''
+
# Change the
'''
Component''' to ''ux-advise''
+
# Update the Status
+
#*
If
the request looks complete and plausible
,
Status -> '''NEW'''
+
#
* If the request seems incomplete or needs explaining, Status ->
'''
NEEDINFO'''
+
# Leave a comment along the lines of:
+
UX Team -- please take a look at this enhancement. Thanks!
−
Some bugs don't belong in Bugzilla at all. For a list of topics that belong elsewhere, see [[QA/BugReport#Not_all_bugs_go_to_Bugzilla|the BugReport page]].
+
<br>
+
''
Some bugs don't belong in Bugzilla at all
''
. For a list of topics that belong elsewhere, see [[QA/BugReport#Not_all_bugs_go_to_Bugzilla|the BugReport page]].
* If one of these bugs is filed in Bugzilla, please change the status to '''RESOLVED NOTOURBUG''' and add the following in a comment:
* If one of these bugs is filed in Bugzilla, please change the status to '''RESOLVED NOTOURBUG''' and add the following in a comment:
Line 84:
Line 83:
your issue, please look at the BugReport wiki page:
your issue, please look at the BugReport wiki page:
https://wiki.documentfoundation.org/QA/BugReport#Not_all_bugs_go_to_Bugzilla
https://wiki.documentfoundation.org/QA/BugReport#Not_all_bugs_go_to_Bugzilla
+
+
+
====Step 3. Search for Duplicates====
+
Duplicates are bugs marked RESOLVED DUPLICATE which are very similar or identical but reported by different users.
+
Such bugs are automatically counted by Bugzilla and available at [https://bugs.libreoffice.org/duplicates.cgi?sortby=count&reverse=1&bug_id=46074%2C53006%2C46901%2C39007%2C38913%2C44664%2C50552%2C36263%2C53482%2C49853%2C46071%2C45081%2C44720%2C37488%2C37405%2C40298%2C43989%2C40571%2C46155%2C36301&sortvisible=0&product=LibreOffice&maxrows=50&changedsince=7 Most Frequently Reported Bugs] page. When triaging please check that list and do a quick search through bugs in Bugzilla to see if there are any duplicates of the bug that you have, but don't need to spend a lifetime on this. As you see more bugs you may remember seeing a similar bug and can easily close the newest of the two (or more) bugs. In general minimizing the amount of duplicate bugs entered into Bugzilla will save time for QA team members.
+
+
'''If you find a duplicate bug skip to step #5'''
+
+
==== Step 4. Check Information ====
+
Checking information is critical for development. What you should look for is the following:
+
# Clear and meaningful summary
+
# Clear problem description
+
# Steps to reproduce the problem -- if not clear from summary and/or description
+
# Attachments -- in many cases attachments are needed to reproduce the problem, if attachment(s) are not provided this can hinder proper fixes
+
+
'''If all information is not properly there, skip to step #5'''
<br />
<br />
−
==== Step
4
. Attempt to Reproduce ====
+
==== Step
5
. Attempt to Reproduce ====
If the bug "passed" the Preparation steps it's time to try to reproduce the bug.<br />
If the bug "passed" the Preparation steps it's time to try to reproduce the bug.<br />
Do just that: Go through the steps necessary and try to reproduce the bug, that simple! When you reproduce it, keep these things in mind:
Do just that: Go through the steps necessary and try to reproduce the bug, that simple! When you reproduce it, keep these things in mind:
Line 94:
Line 109:
<br />
<br />
−
==== Step
5
. Set Status ====
+
==== Step
6
. Set Status ====
This section is the last "mandatory" step of a successful triage and can only be done once steps #1–#4 are done (or #3 if #4 isn't applicable).<br />
This section is the last "mandatory" step of a successful triage and can only be done once steps #1–#4 are done (or #3 if #4 isn't applicable).<br />
Line 113:
Line 128:
<br />
<br />
−
==== Step
6
. Prioritize Bug ====
+
==== Step
7
. Prioritize Bug ====
We currently '''highlight''' only '''critical bugs''' by ''CC''-ing developers, adding special whiteboard entries, keywords, and updating ''MAB''s. See [[#Additional Useful .28Optional.29 Steps|below for more information]].
We currently '''highlight''' only '''critical bugs''' by ''CC''-ing developers, adding special whiteboard entries, keywords, and updating ''MAB''s. See [[#Additional Useful .28Optional.29 Steps|below for more information]].