|
|
| (21 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| = Need to change = | | = Need to change = |
| * [[Issue_Tracker/Status]] - see below for new page | | For Aug 23: |
| * [[Issue_Tracker/Searching]] - ask Torley to update the video (also How to Submit a Bug video) | | * DONE - [[Issue_Tracker/Status]] - made a new section on live page |
| * Minor edits to [[Issue_Tracker/FAQ]]
| | * DONE - Minor edits to [[Issue_Tracker/FAQ]] |
|
| |
|
| | | For Upgrade/Migration on Sept 6/7: |
| = Status =
| | * [[Issue_Tracker/Searching]] - Torley will create new videos week of Aug 30 (after we do test migration) |
| | | * [[Issue_Tracker_Forum_Transcript]] - out of date, maybe should be archived somehow? |
| Here's how Linden Lab uses the workflow status and resolution states:
| | * Missing: Explanation of how JIRA issues are worked from start to finish. (new page for this probably). |
| | |
| ; 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 : 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 Status = Fixed.
| |
| | |
| ; Closed : When the Reporter agrees the issues is fixed in Production, s/he should mark the issue as Closed.
| |
| | |
| ; Resolved : An implicit assignment back to the reporter of the issue. It's 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.
| |
| | |
| ; Needs More Info (Resolution Status = Incomplete) : The issue lacks actionable information. Add the info or it CAN'T be investigated.
| |
| | |
| ; Cannot Reproduce (Resolution Status = 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 Status = Incomplete) :
| |
| | |
| ; Support Issue : The issue does NOT belong in the Issue Tracker, and needs to be handled through the [http://secondlife.com/support Support Portal].
| |
| :; Won't Finish : The assignee or Linden Lab doesn't reasonably believe this issue should or will be fixed.
| |
| :; Duplicate : There's another issue about the same problem/idea.
| |
| :; Expected Behavior : This is NOT a bug and functions by design [http://wiki.secondlife.com/wiki/Issue_Tracker/FAQ#Why_was_my_issue_resolved_with_a_status_of_.22Expected_Behavior.22.3F|Also see this.]
| |
| | |
| :; Under Advisement : An issue that's about [[:Category:Policies|policy]], instead of a technical bug. This status shows that the issue has been viewed and is being discussed by Linden Lab.
| |
| | |
| :; Misfiled : This issue doesn't belong in the Issue Tracker. Often, these are afoul of [[Issue_Tracker/Conduct|our rules]].
| |
| | |
| ; Closed : The final resting place. It's done!
| |
| | |
| After an issue gets Linden attention, [[Issue_Tracker/FAQ#How_do_I_keep_up_with_what.27s_going_on.3F|you can follow along]].
| |
Need to change
For Aug 23:
For Upgrade/Migration on Sept 6/7:
- Issue_Tracker/Searching - Torley will create new videos week of Aug 30 (after we do test migration)
- Issue_Tracker_Forum_Transcript - out of date, maybe should be archived somehow?
- Missing: Explanation of how JIRA issues are worked from start to finish. (new page for this probably).