JIRA - Local help

JIRA tracks issues, which can be bugs, feature requests, or any other tasks you want to track.

Each issue has a variety of associated information including:

  • the issue type
  • a summary
  • a description of the issue
  • the project which the issue belongs to
  • components within a project which are associated with this issue
  • versions of the project which are affected by this issue
  • versions of the project which will resolve the issue
  • the environment in which it occurs
  • a priority for being fixed
  • an assigned developer to work on the task
  • a reporter - the user who entered the issue into the system
  • the current status of the issue
  • a full history log of all field changes that have occurred
  • a comment trail added by users
  • if the issue is resolved - the resolution
Issue Types

JIRA can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section.

For Regular Issues
Bug
A problem which impairs or prevents the functions of the product.
Improvement
An improvement or enhancement to an existing feature or task.
Meta Issue
Describes a general category of problems rather than a specific problem
New Feature
A new feature of the product, which has yet to be developed.
Release
Release QARs
Task
A task that needs to be done.
Translation
For Sub-Task Issues
Sub-task
The sub-task of the issue
Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section.

Showstopper
ONLY the most severe, *confirmed* issues which demand immediate attention from Linden Lab. For example, inability for many Residents to login. IMPORTANT: Abusing this setting will cause revocation of Issue Tracker access. If in doubt, mark "Critical" instead.
Critical
Generally, most crashes (particularly if they're easy to reproduce and affect many), content loss, significant memory leaks, greatly reduced performance, etc.
Major
Major loss or impairment of function, including rarer crashes.
Normal
Minor loss or impairment of function, other problems which have workarounds, or issues that are extremely simple to fix.
Low
Non-critical issues with simple fixes
Nice to have
Issues not yet on the Linden Lab roadmap. See WEB-659 for more info.
Statuses

Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.

Open
The issue is open and ready for the assignee to start work on it.
In Progress
This issue is being actively worked on at the moment by the assignee.
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Resolved
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Fix Pending
Issues that have been fixed in Linden Lab's internal codebase, but not yet deployed in a viewer
Ready for Translation
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Translation In Progress
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Translated
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
In QA
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Passed QA
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Translation Final
Published
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
On Hold
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Editing In Progress
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Edited
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Testing
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Verified
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Verified: Fixed
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Verified: Fix Needed
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Republished
TRANSLATION PROJECT ONLY. More Info: https://wiki.secondlife.com/wiki/Community_Translation_Project
Resolutions

An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.

Fixed
A fix for this issue is available in a public release
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.
Contact Support
Please contact Linden Lab support at http://secondlife.com/support rather than using this issue tracker
Duplicate
The problem is a duplicate of an existing issue.
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.
Misfiled
Issue should be somewhere besides this issue tracker
Needs More Info
The problem is not completely described.
Under Advisement
The problem/idea is being evaluated.
Won't Finish
The problem described is an issue which likely will never be fixed.