Prepare:
← Older revision
Revision as of 20:38, 21 November 2012
(2 intermediate revisions by one user not shown)
Line 36:
Line 36:
==== Prepare ====
==== Prepare ====
In general you'll always want to do the following steps in preparing to triage bugs.
In general you'll always want to do the following steps in preparing to triage bugs.
+
Remember that you can work on bugs only when logged in (please [https://bugs.freedesktop.org/createaccount.cgi create] an account if you do not already have one).
'''1. Find Bugs to Triage'''
'''1. Find Bugs to Triage'''
Line 41:
Line 42:
a) '''FreeDesktop Search'''
a) '''FreeDesktop Search'''
−
Navigate
through fdo (
freedesktop.org)
,
do a custom search for bugs that are a) LibreOffice b) UNCONFIRMED or REOPENED
C
) add whatever other criteria you'd like to query for
.
Once you are there search for a bug that you'd like to triage.
The links below are
direct links to searches, clicking on the link will bring up the fdo result page:
+
Navigate
to LibreOffice's bug tracker system available at [http://bugs.
freedesktop.org
bugs.freedesktop.org] (in short - fdo
)
. After logging in [https://bugs.freedesktop.org/describecomponents.cgi?product=LibreOffice&bug_status=UNCONFIRMED browse] open issues by component or
do a custom search for bugs that are
:
+
+
a)
filed in
LibreOffice
product
+
+
b)
have
UNCONFIRMED or REOPENED
status
+
+
c
) add whatever other criteria you'd like to query for
+
+
Once you are there search for a bug that you'd like to triage.
Custom search for bugs can be build using [https://bugs.freedesktop.org/query.cgi?format=advanced Advanced Search form] or entering search terms in Quick Search field ([https://bugs.freedesktop.org/page.cgi?id=quicksearch.html Bugzilla Quick Search help]). You can also use
+
following
direct links to searches, clicking on the link will bring up the fdo result page:
*[https://bugs.freedesktop.org/buglist.cgi?list_id=8557&field0-0-0=creation_ts&query_format=advanced&bug_status=UNCONFIRMED&bug_status=REOPENED&type0-0-0=greaterthan&value0-0-0=-14d&product=LibreOffice Bugs reported in previous '''2 weeks''']
*[https://bugs.freedesktop.org/buglist.cgi?list_id=8557&field0-0-0=creation_ts&query_format=advanced&bug_status=UNCONFIRMED&bug_status=REOPENED&type0-0-0=greaterthan&value0-0-0=-14d&product=LibreOffice Bugs reported in previous '''2 weeks''']
Line 47:
Line 57:
*[https://bugs.freedesktop.org/buglist.cgi?list_id=8557&field0-0-0=creation_ts&query_format=advanced&bug_status=UNCONFIRMED&bug_status=REOPENED&type0-0-0=greaterthan&value0-0-0=-30d&product=LibreOffice Bugs reported in previous '''1 month''']
*[https://bugs.freedesktop.org/buglist.cgi?list_id=8557&field0-0-0=creation_ts&query_format=advanced&bug_status=UNCONFIRMED&bug_status=REOPENED&type0-0-0=greaterthan&value0-0-0=-30d&product=LibreOffice Bugs reported in previous '''1 month''']
−
* [https://bugs.freedesktop.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]. (
Will
take some time to load as it's quite a long list)
+
* [https://bugs.freedesktop.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.freedesktop.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 '''MacOS '''Bugs, which needs confirmation]
* [https://bugs.freedesktop.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 '''MacOS '''Bugs, which needs confirmation]
b) '''Google Documents Bug Groups'''
b) '''Google Documents Bug Groups'''
−
We are experimenting with a shared document that groups bugs together. Feel free to check it out and assign yourself a sheet(there are anywhere from 1-50 bugs per sheet, all organized by "component" (ie. writer, spreadsheet, etc...
.
)
+
We are experimenting with a shared document that groups bugs together. Feel free to check it out and assign yourself a sheet (there are anywhere from 1-50 bugs per sheet, all organized by "component" (ie. writer, spreadsheet, etc...
)
)
*[https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E Google Documents Group Collaboration]
*[https://docs.google.com/spreadsheet/ccc?key=0ApS-XtOUGGH5dDIwaXN1YnNsM0h4RXFKdVhvb2RRb0E Google Documents Group Collaboration]
Line 57:
Line 68:
'''2. Search for Duplicates'''
'''2. Search for Duplicates'''
−
Don't spend
very
much time on this
but
try to
do a quick search through bugs in freedesktop to see if there are any duplicates of the bug that you have. As you see more bugs you may remember seeing a similar bug and can easily close the newest of the two (or more) bugs
)
.
+
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.freedesktop.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 freedesktop 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'''
'''If you find a duplicate bug skip to step #5'''
Line 64:
Line 76:
'''3. Check Information'''
'''3. Check Information'''
Checking information is critical for development. What you should look for is the following:
Checking information is critical for development. What you should look for is the following:
−
# Clear and meaningful
title
+
# Clear and meaningful
summary
−
# Clear problem
summary
+
# Clear problem
description
−
# Steps to reproduce problem -- if not clear from summary and/or
title
+
# Steps to reproduce
the
problem -- if not clear from summary and/or
description
−
# Attachments -- in many cases attachments are needed to
see
problem, if attachment(s) are not provided this can hinder proper fixes
+
# 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'''
'''If all information is not properly there, skip to step #5'''
Line 86:
Line 98:
# NEW - Confirmed bug, all information necessary is there
# NEW - Confirmed bug, all information necessary is there
# NEEDINFO - All information needed to attempt replication is not included with the bug report
# NEEDINFO - All information needed to attempt replication is not included with the bug report
−
# RESOLVED - This category comes with several options, if you can't replicate the bug, RESOLVED is the appropriate STATUS, see HERE for more information.
+
# RESOLVED - This category comes with several options, if you can't replicate the bug, RESOLVED
WORKSFORME
is the appropriate STATUS, see HERE for more information.
# INVALID - There are many reasons why a bug can be determined to be invalid but this usually requires input from other QA members. If you come across a bug that you believe to be invalid, best bet it to get a second opinion from the QA IRC channel or send an email out to the mailing list explaining why you believe the bug to be invalid
# INVALID - There are many reasons why a bug can be determined to be invalid but this usually requires input from other QA members. If you come across a bug that you believe to be invalid, best bet it to get a second opinion from the QA IRC channel or send an email out to the mailing list explaining why you believe the bug to be invalid
# UNCONFIRMED - This is the status given to all new bugs that have not gone through triage process
# UNCONFIRMED - This is the status given to all new bugs that have not gone through triage process