Issue States in the Public Issue Tracker (JIRA)
All issues in the Public Issue Tracker have an assigned state to indicate status. Below is a list of all possible states, and a brief description of each.
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 reporter 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".
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. The Resolved state is accompanied by a reason for the issue's resolution:
Fixed - The bug is fixed in a public release of Second Life.
Fixed Internally - The bug is fixed in a version of the code that should soon be publicly available.
Won't Fix - The assignee doesn't believe this issue should ever be fixed.
Duplicate - There is some other issue that describes the same problem/idea.
Needs More Info - This issue does not provide enough information about itself.
Cannot Reproduce - Linden Lab could not reproduce the bug. Issues that can't be reproduced will eventually be closed.
Misfiled - The issue does not belong in this issue tracker.
Closed - The issue has been resolved, and the issue reporter is satisfied with the results.
What's the difference between "Fixed Internally" and "Fixed" resolutions?
"Fixed" means the fix is available in the live Second Life release, right now, while "Fixed Internally" means the fix has been made within Linden Lab and has not been released publicly yet. It may need to undergo extra care, like quality assurance, or requires merging from a branch, before being available to you. Think of it as a "We're almost there... coming soon!" notice.