Difference between revisions of "Bug Tracker/Status"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
=== Available states === | === Available states === | ||
Here | Here's how Linden Lab uses the various resolution states: | ||
; 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) | ; 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) | ||
| Line 31: | Line 31: | ||
* When the change is available in a new version of Second Life, it is resolved as '''"Fixed"'''. | * 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"'''. | * 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]] | |||
Revision as of 14:56, 15 October 2009
Status of your Issue
Available states
Here's how Linden Lab uses the various resolution states:
- 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)
- In Progress
- This is how a developer signals to everyone that he/she is working on the issue.
- Reopened
- same as "Open". Even though it was closed before, it is now reported as still a problem that needs attention.
- 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.
- Fixed
- means that the bug is fixed in a public release of Second Life.
- Fix Pending
- means that the bug is fixed in a version of the code that should soon be publicly available.
- 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.
- Won't Finish
- means that the assignee or Linden Lab doesn't believe this issue should or will be fixed in any foreseeable future.
- Duplicate
- means that there's some other issue that describes the same problem/idea.
- 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!
After the issue gets Linden attention, others can still follow along what is the status of the issue:
- 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 Quality Assurance Team and our community, the status is changed from "Resolved" to "Closed".