← Older revision
Revision as of 2013-05-27T08:34:57
(3 intermediate revisions by one user not shown)
Line 2:
Line 2:
{{Menu}}
{{Menu}}
{{Menu.QA}}
{{Menu.QA}}
−
{{OrigLang|}}
−
This page is about the '''NEEDINFO''' state of the [[QA/Bugzilla/Fields/Status|Status]] Field in [[Bugzilla]].
+
=== Purpose of this Page ===
+
This page is about the '''NEEDINFO''' state of the [[QA/Bugzilla/Fields/Status|Status]] Field in [[Bugzilla]]
. It is dedicated to explaining and clarifying the purpose of '''NEEDINFO''' as well as describing the steps which QA can/will take in addressing '''NEEDINFO''' bugs that never get the requested information
.
−
=
= Purpose of this Page ==
+
=== The Meaning of NEEDNIFO
=
==
−
This page is dedicated to explaining and clarifying the purpose of '''NEEDINFO''' as well as describing the steps which QA can/will take in addressing '''NEEDINFO''' bugs that never get the requested information.
+
−
+
−
== The Meaning of NEEDNIFO ==
+
Members of the QA team had a lengthy discussion about the meaning of '''NEEDINFO'''. Changes were proposed in order to identify what exactly '''NEEDINFO''' means. Up until now '''NEEDINFO''' has been a status which exists in perpetuity, where it often times sits indefinitely as the user is no longer following their bug and therefore will never provide the information requested. In general there was agreement that this status should give us an idea of what bugs will realistically ever get attention again, not just be a place holder for any bug that we request information and then just sits indefinitely. So '''NEEDINFO''' definition:
Members of the QA team had a lengthy discussion about the meaning of '''NEEDINFO'''. Changes were proposed in order to identify what exactly '''NEEDINFO''' means. Up until now '''NEEDINFO''' has been a status which exists in perpetuity, where it often times sits indefinitely as the user is no longer following their bug and therefore will never provide the information requested. In general there was agreement that this status should give us an idea of what bugs will realistically ever get attention again, not just be a place holder for any bug that we request information and then just sits indefinitely. So '''NEEDINFO''' definition:
: ''"'''NEEDINFO''' represents a bug that cannot be reproduced and fixed until more information is provided. If a bug has been in this state for more than 180 days, it is considered as dead end, and can be closed."''
: ''"'''NEEDINFO''' represents a bug that cannot be reproduced and fixed until more information is provided. If a bug has been in this state for more than 180 days, it is considered as dead end, and can be closed."''
−
== Setting Bugs to NEEDINFO Status ==
+
=
== Setting Bugs to NEEDINFO Status
=
==
In order to fulfill this goal of cleaning the '''NEEDINFO''' bugs QA will try to do the following:
In order to fulfill this goal of cleaning the '''NEEDINFO''' bugs QA will try to do the following:
# Be very clear about what information is being requested
# Be very clear about what information is being requested
Line 21:
Line 18:
# Let user know the appropriate status to set the bug to after information is requested
# Let user know the appropriate status to set the bug to after information is requested
−
== When Information Is Provided ==
+
=
== When Information Is Provided
=
==
The information provider sets the status back to '''UNCONFIRMED''' when the questions are answered.
The information provider sets the status back to '''UNCONFIRMED''' when the questions are answered.
−
== When Information Is Not Provided ==
+
=
== When Information Is Not Provided
=
==
The QA team has a new email which we will be using in the following way for '''NEEDINFO''':
The QA team has a new email which we will be using in the following way for '''NEEDINFO''':
# '''After 180 Days: '''Point user to this wiki, request information again, let user know that if requested information is already there, to appropriately set the status of the bug so we move the bug forward.
# '''After 180 Days: '''Point user to this wiki, request information again, let user know that if requested information is already there, to appropriately set the status of the bug so we move the bug forward.
# '''30 Days Later: '''Close the bug as [[QA/Bugzilla/Fields/Status/INVALID|INVALID]] because of lack of information, let user know that if they are still experiencing the bug they can open it back up as [[QA/Bugzilla/Fields/Status/INVALID|UNCONFIRMED]] if they provide requested information.
# '''30 Days Later: '''Close the bug as [[QA/Bugzilla/Fields/Status/INVALID|INVALID]] because of lack of information, let user know that if they are still experiencing the bug they can open it back up as [[QA/Bugzilla/Fields/Status/INVALID|UNCONFIRMED]] if they provide requested information.
−
== Rationale ==
+
=
== Rationale
=
==
In general there were several reasons why this idea was agreed upon:
In general there were several reasons why this idea was agreed upon:
* Relatively standard across large projects
* Relatively standard across large projects
Line 37:
Line 34:
* General reminder that a bug exists, many times users simply forgot
* General reminder that a bug exists, many times users simply forgot
* Give NEEDINFO a specific definition that is workable (similar to second point)
* Give NEEDINFO a specific definition that is workable (similar to second point)
−
+
−
== Relative Links ==
+
−
NEED LINK FOR EMAIL THREAD
+
−
NEED LINK FOR MINUTES
+
−
Any other useful links?
+
[[Category: QA]]
[[Category: QA]]