User:Sue Linden/JIRA Updates

Need to change

• Issue_Tracker/Status - see below for new page
• Issue_Tracker/Searching - ask Torley to update the video (also How to Submit a Bug video)
• Minor edits to Issue_Tracker/FAQ

Status

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

Pending

Initial state when an issue/ticket is created. All issues in "Pending" will be reviewed and triaged.

Acknowledged

When an issue has been imported to an internal Linden Lab project, it will be marked as Acknowledged.

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.

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.

Closed

Resolution = Fixed

When the Reporter agrees the issues 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.

Needs More Info (Resolution = Incomplete)

The issue lacks actionable information. Add the info or it CAN'T be investigated.

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.

Deferred (Resolution = Incomplete)

Support Issue

The issue does NOT belong in the Issue Tracker, and needs to be handled through the Support Portal.

Expected Behavior

This is NOT a bug and functions by design see this.

Misfiled (Resolution = Not Applicable)

This issue doesn't belong in the Issue Tracker. Often, these are afoul of our rules.

Closed

The final resting place. It's done!

After an issue gets Linden attention, you can follow along.

Transition Plans from Old to New Workflow

Definitions
Status= Step in the workflow; the stage the issue is currently at in its lifecycle; ie the box in the workflow diagram
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.

Resolution	Description	Migration Plans
Fixed	A fix for this issue is available in a public release	remains as is
Cannot Reproduce	All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.	Change to "Cannot Reproduce" Status, Resolution = Incomplete
Contact Support	Please contact Linden Lab support at http://secondlife.com/support rather than using this issue tracker	Change to "Contact Support" Status, Resolution = Incomplete
Duplicate	The problem is a duplicate of an existing issue.	remains as is
Expected Behavior	Often the system is behaving exactly as designed, but it can look wrong if you're not aware of the reasons behind the behavior. This status is used for such cases.	Change to "Expected Behavior" Status, Resolution = Not Applicable
Misfiled	Issue should be somewhere besides this issue tracker	Change to "Misfiled" Status, Resolution = Not Applicable
Needs More Info	The problem is not completely described.	Change to "Needs More Info" Status, Resolution = Incomplete
Under Advisement	The problem/idea is being evaluated.	Change to "Deferred" Status, Resolution = Incomplete
Won't Finish	The problem described is an issue which likely will never be fixed.	remains as is
Not Applicable	Ticket is not applicable because it is filed in the wrong system, is a support issue, etc.	new
Incomplete	Ticket is incomplete because it needs more information, cannot be reproduced, etc.	new