Difference between revisions of "Bug Tracker/Status"

From Second Life Wiki
Jump to navigation Jump to search
 
(32 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Status of your Issue ==
Here's how Linden Lab uses the workflow status and resolution field:


=== Available states ===
; Awaiting Review : Initial state when an issue/ticket is created or when it is reopened closed state. All issues in in this state will be reviewed and triaged.


Here's how Linden Lab uses the various resolution states:
; Been Triaged : This state indicates that the issue is being reviewed by Linden Lab.


; Open : This is an issue that belongs to the Assignee to resolve.  The Assignee may fix the issue, or kick the issue back to the person who reported it, by marking it "Resolved" (see below)
; Accepted : When an issue has been imported to an internal Linden Lab project, it will be marked as Accepted.


; In Progress : This is how a developer signals to everyone that he/she is working on the issue.
; Needs More Info : The issue lacks actionable information. Add the info or it CAN'T be investigated.


; Reopened : same as "Open". Even though it was closed before, it is now reported as still a problem that needs attention.
; Information Provided : The issue has been updated with the necessary information.


; Resolved : This is an implicit assignment back to the reporter of the issue.  It is not closed yet, but rather in a state of limbo that depends on the resolution.  It's up to the Reporter to decide whether to reopen an issue, or close it.
; Closed :
:; Fixed : means that the bug is fixed in a public release of Second Life.
:; Resolution = Contact Support : The issue does NOT belong in the Bug Tracker, and needs to be handled through the [http://secondlife.com/support Support Portal] or [http://blogs.secondlife.com/community/answers Second Life Answers].
:; Fix Pending: means that the bug is fixed in a version of the code that should soon be publicly available.
:; Resolution = Expected Behavior : This is NOT a bug and functions by design [[Not_a_bug|See Expected Behavior aka Not a Bug.]]
:; Contact Support : the issue in the Pjira is one that needs to be handled through the support team and the Resident needs to fill out a support ticket.
:; Resolution = Duplicate : There's another issue about the same problem.
:; Won't Finish : means that the assignee or Linden Lab doesn't believe this issue should or will be fixed in any foreseeable future.
:; Resolution = Unactionable : Problem described in the ticket is not in a form that action can be taken (i.e. it's too broad)
:; Duplicate : means that there's some other issue that describes the same problem/idea.
:; Resolution = Not Applicable : The Reporter has decided to close the issue.
:; Expected Behavior : the issue being discussed is not a bug and functions as it does by design.
:; Needs More Info : this issue lacks enough information.  Please add that information or it CANNOT be investigated further.
:; Under Advisement : this is used by Linden Lab for issues that tend to fall more in the category of Policy rather than being just a technical bug.  This is used to let the community know that the Pjira has been viewed and is being discussed.
:; Cannot Reproduce : this means that following the stated steps still does not show the problem.  Perhaps there is additional settings/actions or factors that need to be true in order for the problem to occur.  Please provide an even more detailed description of how to reproduce a problem.  Issues that can't be reproduced will eventually be closed.
:; Misfiled : this issue doesn't belong in this issue tracker.


; Closed : The final resting place.  It's done!
== Diagram of Workflow ==


[[Image:BUGworkflow.png]]


After the issue gets Linden attention, others can still follow along what is the status of the issue:
Note:
 
* Diagram does not have all the transition arrows.
* Once the changes are completed and awaiting release to the public, the bug is resolved to show '''"Fix Pending"'''.
* When the change is available in a new version of Second Life, it is resolved as '''"Fixed"'''.
* Generally, after being confirmed as fixed & done by Linden Lab's [[QA Portal|Quality Assurance Team]] and our community, the status is changed from "Resolved" to '''"Closed"'''.
 
[[Category:Issue Tracker]]

Latest revision as of 09:53, 6 September 2012

Here's how Linden Lab uses the workflow status and resolution field:

Awaiting Review
Initial state when an issue/ticket is created or when it is reopened closed state. All issues in in this state will be reviewed and triaged.
Been Triaged
This state indicates that the issue is being reviewed by Linden Lab.
Accepted
When an issue has been imported to an internal Linden Lab project, it will be marked as Accepted.
Needs More Info
The issue lacks actionable information. Add the info or it CAN'T be investigated.
Information Provided
The issue has been updated with the necessary information.
Closed
Resolution = Contact Support
The issue does NOT belong in the Bug Tracker, and needs to be handled through the Support Portal or Second Life Answers.
Resolution = Expected Behavior
This is NOT a bug and functions by design See Expected Behavior aka Not a Bug.
Resolution = Duplicate
There's another issue about the same problem.
Resolution = Unactionable
Problem described in the ticket is not in a form that action can be taken (i.e. it's too broad)
Resolution = Not Applicable
The Reporter has decided to close the issue.

Diagram of Workflow

BUGworkflow.png

Note:

  • Diagram does not have all the transition arrows.
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Bug_Tracker/Status&oldid=1172483"