page1
Is a document test case
relevant and possible
for bug?
Is bug currently in
unconfirmed status?
YES
NEEDINFO
YES
Does the bug have
comments from
LibreOffice staff?
Yes
NEW
Is there enough information
for you to attempt to replicate
bug?
ATTEMPT
TO
REPLICATE
NO
Does test case display bug
for you?
**NOTES**
1. This is just a general guideline, feel free to do it another way, just be consistent
2. Before starting you should ask yourself, IS THIS ACTUALLY A BUG!? If it's not, mark as RESOLVED → NOT A BUG & leave a comment for user explaining why you did so, let them know they can comment back if they disagree.
3. After confirming it is a bug, you should ask yourself, IS THIS OUR BUG, if it's not, mark as RESOLVED → NOT OUR BUG & leave a comment explaining yourself.
We should make an extra effort as QA staff to leave a comment any time we change something, it's important to let the user base know our rationale so that they understand and are given the opportunity to change our mind. Also, thanking bug reporters for sticking with it and helping us make LibreOffice is just a good thing to do ;)
NO
YES
YES
NO
Unconfirmed Bug Status Triage
Flowchart Suggestion(s)
Does comment request
additional information
and/or documentation
for bug?
Leave comment letting
user and commenter(s) know that
you have changed status to
NEEDINFO and once requested
information/documentation is
provided they should change
status back to UNCONFIRMED.
THANK BUG REPORTER
FOR HELPING US!
Yes
Does user provide
test case?
NO
Request that the member(s)
of staff who have commented
confirm bug (mark as NEW)
and prioritize bug if possible.
THANK EVERYONE :)
NEEDINFO
Leave comment letting
user and commenter(s) know
That you have changed status to
NEEDINFO and once requested
information/documentation is
provided they should change
status back to UNCONFIRMED.
THANK BUG REPORTER
FOR HELPING US!
Leave comment letting
user and commenter(s) know that
you have changed status to
NEW and that it means
you have confirmed bug.
provide details about
replication attempt.
Provide your system info and
build info.
PRIORITIZE
THANK EVERYONE :)
YES
Are you able to
replicate bug?
YES
NEW
Leave comment letting
user and commenter(s) know that
you have changed status to
NEW and that it means
you have confirmed bug.
provide details about
replication attempt.
Provide your system info and
build info.
PRIORITIZE
THANK EVERYONE :)
RESOLVED
WORKSFORME
Leave comment letting
user and commenter(s) know that
you have changed status to
RESOLVED → WORKSFORME,
Tell reporter if it's still a
bug for them to
change status back to
UNCONFIRMED and
provide more details if possible
NO
RESOLVED
WORKSFORME
Leave comment letting
user and commenter(s) know that
you have changed status to
RESOLVED → WORKSFORME,
tell reporter if it's still a
bug for them to
change status back to
UNCONFIRMED and
provide more details if possible
NO
NO
NEEDINFO
Leave comment letting
user and commenter(s) know
That you have changed status to
NEEDINFO and once requested
information/documentation is
provided they should change
status back to UNCONFIRMED.
THANK BUG REPORTER
FOR HELPING US!