Difference between revisions of "Public Issue Tracker (JIRA) Overview"
Fritz Linden (talk | contribs) (Initial Parature import) |
Yoz Linden (talk | contribs) m (1 revision) |
||
| Line 1: | Line 1: | ||
{{Seal}} | {{Seal}} | ||
{{KBwarning| '''Warning:''' The JIRA Issue Tracker is not for technical support-type requests. If you're looking for account-specific help, please use our | |||
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. | |||
{{KBwarning| '''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. | |||
}} | }} | ||
{{KBnote| '''Note:''' All submissions to the Public Issue Tracker are governed by the | |||
{{KBnote| '''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== | ==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 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". | 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. | 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== | ==Caveats== | ||
The Public Issue Tracker is not for technical support, so please do ''not'' enter issues like: | 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!" | * "I keep crashing and want it to stop now!" | ||
| Line 25: | Line 42: | ||
* "The sim I'm in is LAGGIN BAD" | * "The sim I'm in is LAGGIN BAD" | ||
* "How do I build a house?" | * "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 | |||
'''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. | |||
[[Category:Bugs and the Public JIRA]] | [[Category:Bugs and the Public JIRA]] | ||
[[Category:Public Issue Tracker (JIRA)]] | [[Category:Public Issue Tracker (JIRA)]] | ||
[[Category:Knowledge Base]] | [[Category:Knowledge Base]] | ||
Revision as of 15:28, 5 October 2009
This article is part of the Extended Second Life Knowledge Base that includes advanced and specialized information. This information was originally provided by Linden Lab, but is not actively maintained nor guaranteed to be accurate. Linden Lab does not certify nor assume any responsibility for this information.
See the official Second Life Knowledge Base for the most current information.
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: 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: 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.