Bug Tracker/FAQ

From Second Life Wiki
< Bug Tracker
Revision as of 08:03, 10 September 2010 by Sue Linden (Talk | contribs)

Jump to: navigation, search
KBtip2.png Tip: These are further details on how to use the Bug Tracker.

What's the difference between Bugs & New Features?

  • Bug - Something does not work correctly compared to the way it was designed or should be expected to.
  • New Feature - Something that Second Life doesn't do, but you think it would be a great idea or improvement if it could.

How do I search?

What kind of behavior is allowed on the Bug Tracker?

^ Useful, helpful behavior. :)

What software powers your Bug Tracker?

JIRA from Atlassian, which you can read the general documentation to. If you find a bug with JIRA itself, contact Atlassian.

How do I customize my settings?

Can I write my bug report in another language?

While we have a growing number of Lindens who are multilingual, to have your issue understood broadly by the Linden Lab's developers, please have a friend help you with an English translation.

How do I keep up with what's going on?

On the left of each issue is a Watch it link you can click. When the issue is updated, you'll get an email notification. You can also view Your Watches.

Check the Release Notes for what's new in Second Life. Release Notes highlight features and bug fixes, as well as known issues to be aware of. This context may help you understand whether a change was intentional.

Also, make sure your graphics drivers are updated. Many historical bugs have been fixed by newer drivers.

Our Bug Triagers review issues on a regular basis; feel free to join in! Our engineers may require additional information from the issue reporter or other contributors.

What are Projects and Components?

  • Projects - Used to sort issues into sensible groups. One big project is "VWR" for our Second Life Viewer, the software package you download to use Second Life.
  • Components - The specific area of a problem within a project.

More Projects and Components are added over time as needed.


  • Second Life Viewer - VWR
    • Component = Avatar/Character - "My avatar clothing is all black after installing a video driver update"
    • Component = Inventory - "Objects in my inventory don't remain sorted in the correct order after relogging"
  • Second Life Service - SVC
    • Component = Performance and/or Teleport - "Server performance decreases when several avatars teleport into the Region at once"
    • Component = Scripts - "My scripted objects are not able to talk to the outside world after Second Life Grid downtime"
  • Second Life Website - WEB
    • Component = wiki.secondlife.com - "Wiki blocks login for Residents with a 'y' in their name"
    • Component = jira.secondlife.com. - "The Bug Tracker always forces me to authenticate, even if I save my login information"

What is the "SEC" Project?

Who is WorkingOnIt Linden?

A group account used to mark status when an issue is being investigated internally by Linden Lab. This is more communicative than the issue being "Unassigned". Various Lindens can access the account.

What do the different resolution statuses mean?

Why was my issue resolved with a status of "Expected Behavior"?

Often, the Second Life software is behaving exactly as designed, but it can seem wrong if you're not aware of reasons behind the behavior. "Expected Behavior" is used for such cases — where what you saw happen was not a bug, but you're asking for a new behavior we haven't thought of yet.

If you would like to push for a change in that behavior:

  1. First search to make sure someone else hasn't already requested this feature!
    1. If it has already been requested, vote and add your comments to the issue.
  2. Go to the issue's page and click Reopen Issue on the left. Be sure to state WHY in the comments.
  3. Then, click Edit on the left, change the Issue Type to New Feature by moving it.
  4. Go through the steps and click Move to confirm.

What do the different priority levels indicate?

  • Showstopper - an issue that could (or did) cause disastrous consequences. For example critical loss of data, critical loss of system availability, critical loss of security, critical loss of safety.
  • Severe - an issue that could (or did) cause very serious consequences. For example a function is severely broken, cannot be used and there is no workaround.
  • Major - an issue that could (or did) cause significant consequences, but there is a workaround. For example: A function is badly broken but workaround exists.
  • Minor (default) - an issue that could (or did) cause small or negligible consequences. Easy to recover or workaround. For example: misleading error messages, displaying output in a font or format other than what the resident desired.
  • Trivial - an issue that can cause no negative consequences. Such defects normally produce no erroneous outputs. For example: simple typos in documentation, bad layout or mis-spelling on screen.