Public Issue Tracker (JIRA) Overview

Template:Needs Translation/KB/de Template:Needs Translation/KB/es Template:Needs Translation/KB/el Template:Needs Translation/KB/fr Template:Needs Translation/KB/he Template:Needs Translation/KB/it Template:Needs Translation/KB/ja Template:Needs Translation/KB/ko Template:Needs Translation/KB/nl Template:Needs Translation/KB/hu Template:Needs Translation/KB/no Template:Needs Translation/KB/da Template:Needs Translation/KB/sv Template:Needs Translation/KB/tr Template:Needs Translation/KB/pl Template:Needs Translation/KB/pt Template:Needs Translation/KB/ru Template:Needs Translation/KB/th Template:Needs Translation/KB/uk Template:Needs Translation/KB/zh-Hans Template:Needs Translation/KB/zh-Hant

/KB

add versioning

The public issue tracker, known as "Public JIRA", "PJIRA", or just "JIRA", is an issue-tracking project management tool made by Atlassian that is located at http://jira.secondlife.com. It's used by the Second Life open source initiative to organize issues (i.e. bugs and feature requests) submitted by the Second Life community into a searchable database. You, too, can submit issues you find when using the open source or standard versions of Second Life. Please familiarize yourself with the information on this page before using JIRA.

Warning: The JIRA Issue Tracker is not for technical support-type requests. If you're looking for account-specific help, please use our support resources.

Note: All submissions to the Public Issue Tracker are governed by the Second Life Contribution Agreement. By submitting patches and other information, you acknowledge that you've read, understood, and agreed to those terms.

How it works

Bug reports created in JIRA are composed of a description of the problem and, if possible, a reproduction. New features are composed of descriptions of the proposed feature and how it should work. Both types of issues then get contributions from other users, such as better or simpler descriptions and reproductions, and popular issues accumulate votes from other users. Programmers in the open source community can attach "patches", changes to the code that fix or implement the issue. These votes, as well as events like bug triages, help prioritize the issues. Those which are acknowledged are "imported" into Linden Lab's private copy of JIRA.

After the issue gets Linden Lab developer attention, others can still continue to help. Once the changes are completed and awaiting release to the public, the bug is marked as "resolved - fixed internally". When the change has been made available, it is marked "resolved - fixed", and when confirmed to the satisfaction of most users, "closed - fixed".

In addition to "fixed internally" and "fixed", an issue can also be resolved or closed if it appears to be a duplicate of another issue, unreproducible, misfiled, not a bug, incomplete, etc.

Caveats

The Public Issue Tracker is not for technical support, so please do not enter issues like:

• "I keep crashing and want it to stop now!"
• "Someone stole my L$"
• "The sim I'm in is LAGGIN BAD"
• "How do I build a house?"
• More examples of misfiled issues

Entering misfiled issues which are not actionable and do not contain clear instructions makes it harder for your fellow Residents to use the Issue Tracker. If you are looking for personal assistance, please send your message to the right place by contacting Support, and be sure to include useful details to help us help you. Before reporting issues, we recommend you thoroughly search the support resources first and look for the latest news and status reports on the Official Linden Blog.