Difference between revisions of "Bug Tracker/Status"

From Second Life Wiki
Jump to: navigation, search
(Transition to New Resolutions on 2010/08/24)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
Here's how Linden Lab uses the workflow status and resolution field:
 
Here's how Linden Lab uses the workflow status and resolution field:
  
; Waiting Review : Initial state when an issue/ticket is created or when it is reopened from a resolved or closed state. All issues in in this state will be reviewed and triaged.
+
; 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.
  
; Acknowledged : After we upgrade (planned for Sept 7): When an issue has been imported to an internal Linden Lab project, it will be marked as Acknowledged. We're installing a custom tool to enable syncing between internal and external projects (ie VWR, SVC, WEB). <br/> Prior to upgrade: Acknowledge is all issues that were In Progress.
+
; Been Triaged : This state indicates that the issue is being reviewed by Linden Lab.
  
; Fix Pending : When the imported issue has passed QA internally, then the public issue will change to Fix Pending. The bug is fixed in a version of the code that should soon be publicly available.
+
; Accepted : When an issue has been imported to an internal Linden Lab project, it will be marked as Accepted.
  
; Released (Resolution = Fixed) : When the imported issue has been released (when it's marked as Closed), then the public issue will be marked as Released and the Resolution = Fixed.
+
; Needs More Info : The issue lacks actionable information. Add the info or it CAN'T be investigated.
  
; Closed :
+
; Information Provided : The issue has been updated with the necessary information.
:; Resolution = Fixed : When the Reporter agrees the issue is fixed in Production, s/he should mark the issue as Closed.
+
:; Resolution = Won't Finish : The assignee or Linden Lab doesn't reasonably believe this issue should or will be fixed.
+
:; Resolution = Duplicate : There's another issue about the same problem/idea. See the issues linked to it.
+
  
; Needs More Info (Resolution = Incomplete) : The issue lacks actionable information. Add the info or it CAN'T be investigated.
+
; Closed :
 
+
:; 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].
; Cannot Reproduce (Resolution = Incomplete) : Following the stated steps does NOT show the problem. Please provide a solid description of how to reproduce the problem, otherwise it's like finding Bigfoot. Issues that can't be reproduced will eventually be closed.
+
:; Resolution = Expected Behavior : This is NOT a bug and functions by design [[Not_a_bug|See Expected Behavior aka Not a Bug.]]
 
+
:; Resolution = Duplicate : There's another issue about the same problem.
; Deferred (Resolution = Incomplete) : The problem/idea is being evaluated but will not be worked on at the moment.
+
:; 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.
; Contact Support (Resolution = Not Applicable) : The issue does NOT belong in the Issue Tracker, and needs to be handled through the [http://secondlife.com/support Support Portal] or [http://blogs.secondlife.com/community/answers Second Life Answers].
+
 
+
; Expected Behavior (Resolution = Not Applicable) : This is NOT a bug and functions by design [[Not_a_bug|See Expected Behavior aka Not a Bug.]]
+
 
+
; Misfiled (Resolution = Not Applicable) : This issue doesn't belong in the Issue Tracker. Often, these are afoul of [[Issue_Tracker/Conduct|our rules]].
+
 
+
After an issue gets Linden attention, [[Issue_Tracker/FAQ#How_do_I_keep_up_with_what.27s_going_on.3F|you can follow along]].
+
  
 
== Diagram of Workflow ==
 
== Diagram of Workflow ==
  
[[Image:PJIRA-proposed-workflow-v3.jpg]]
+
[[Image:BUGworkflow.png]]
  
Note:  
+
Note:
 
* Diagram does not have all the transition arrows.
 
* Diagram does not have all the transition arrows.
* A '''terminal state''' is a state that's not a middle step in a workflow, and would frequently be the last state for an issue. "Support Issue" is a good example.
 
 
== Priority Definitions ==
 
* '''Showstopper''' - a issue that could (or did) cause disastrous consequences. For example critical loss of data, critical loss of system availability, critical loss of security, critical loss of safety.
 
* '''Severe''' - a issue that could (or did) cause very serious consequences. For example a function is severely broken, cannot be used and there is no workaround.
 
* '''Major''' - a issue that could (or did) cause significant consequences, but there is a workaround. For example: A function is badly broken but workaround exists.
 
* '''Minor''' (default) - a issue that could (or did) cause small or negligible consequences. Easy to recover or workaround. For example: misleading error messages, displaying output in a font or format other than what the resident desired.
 
* '''Trivial''' - a issue that can cause no negative consequences. Such defects normally produce no erroneous outputs. For example: simple typos in documentation, bad layout or mis-spelling on screen.
 
 
 
== Transition to New Resolutions on 2010/08/24 ==
 
 
'''Definitions'''<br />
 
''Status'' = Step in the workflow; the stage the issue is currently at in its lifecycle; ie the box in the workflow diagram <br />
 
''Resolution'' = a record of the issue's resolution. If Resolution is blank, the issue is "Unresolved." If Resolution has a value, the issue is "Resolved" and will appear crossed out in JIRA. This is regardless of the workflow status.
 
 
{| class="lltable" border=1
 
! Resolution !! Migration Plans
 
|-
 
| Fixed
 
| No change
 
|-
 
| Duplicate
 
| No change
 
|-
 
| Won't Finish
 
| No change
 
|-
 
| Not Applicable
 
| New
 
|-
 
| Incomplete
 
| New
 
|-
 
| Cannot Reproduce
 
| Change to "Cannot Reproduce" Status, Resolution = Incomplete
 
|-
 
| Contact Support
 
| Change to "Support Issue" Status, Resolution = Incomplete
 
|-
 
| Expected Behavior
 
| Change to "Expected Behavior" Status, Resolution = Not Applicable
 
|-
 
| Misfiled
 
| Change to "Misfiled" Status, Resolution = Not Applicable
 
|-
 
| Needs More Info
 
| Change to "Needs More Info" Status, Resolution = Incomplete
 
|-
 
| Under Advisement
 
| Change to "Deferred" Status, Resolution = Incomplete
 
|}
 
 
[[Category:Issue Tracker]]
 

Latest revision as of 10: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.