Difference between revisions of "Bug Tracker"

From Second Life Wiki
Jump to: navigation, search
(Want to know more?)
Line 64: Line 64:
* '''[[Bug_Tracker/FAQ|Read the Bug Tracker FAQ]]''' - If your question wasn't answered above, see this. Highlights include:
* '''[[Bug_Tracker/FAQ|Read the Bug Tracker FAQ]]''' - If your question wasn't answered above, see this. Highlights include:
** [[Bug_Tracker/Searching|How to search]]
** [[Bug_Tracker/Searching|How to search]]
** [[Bug_Tracker/Conduct|Code of conduct]]
** [[Linden_Lab_Official:Community_Participation_Guidelines|Community Participation Guidelines]]
** [[Bug_Tracker/Status|Resolution statuses]]
** [[Bug_Tracker/Status|Resolution statuses]]
* '''[[:Category:Bug Tracker|Visit the Bug Tracker category]]''' - All pages related to the Bug Tracker.
* '''[[:Category:Bug Tracker|Visit the Bug Tracker category]]''' - All pages related to the Bug Tracker.
[[Category:Bug Tracker]]
[[Category:Bug Tracker]]

Revision as of 10:17, 21 January 2011

Is a feature not working as expected in your Second Life? You may have found a bug!


What's a bug?

An unintended computer problem which happens for more than one person under the same conditions.

What's not a bug?

Being "Ruthed" was a common visual bug before we fixed it.

What's a bug report?

A description of a bug, shared by you with us. Useful bug reports are:

  • Easy-to-follow - Ever given driving directions, where you emphasize landmarks to watch for? Bug reports should be like that: they have a sensible order and a friend can follow your steps.
  • Reproducible - Sadly, some bugs are like Bigfoot — hard to find evidence of. But many bugs happen reliably after following a series of steps. Confirm a bug so we can catch it in the wild.
  • NOT account-specific, support issues - Individual situations that desire a response, such as a billing problem, are different! For those, visit our Support Portal.

With that in mind:

  1. Go to our Bug Tracker and read the instructions.
  2. Search the Bug Tracker to see if the bug has already been reported. It's comforting to know someone else has the same problem.
  3. If you find no matches, write a bug report including (1) steps to follow, (2) what you expected to happen, and (3) what happened instead. If you're able to provide pictures, video, or logs in addition to text, even better.

The goal is to show Linden Lab what you see, so we can see it too, then hunt down and fix the bug.

I'm not a geek and I need help!

Don't worry, everyone was new once. There's lots of discussion on the Bug Tracker where experienced Residents help new bug reporters.

We also hold inworld bug triages where you can add bugs to the agenda beforehand, then discuss with Lindens and Residents.

What if Second Life is having a widespread service issue right now?

Generally, login problems, teleport failures, and such are shown on our Grid Status Reports and since we're already working on it, there's no need to file a bug report.

What if the bug I found is really serious and shouldn't be shared?

Learn about our Security Issues steps for exploits that compromise real-life identity, destroy content, and other serious issues that need discretion to be fixed ASAP.

I reported a bug but it hasn't been fixed! Why?

We fix many bugs, but it's unrealistic to expect that we'll fix all of them. Let's look at this closer:

  • What do we know? We can't act on bugs that we can't reproduce or don't have enough info about. It's like telling the police a crime happened without evidence. (While bugs aren't criminals, they certainly cause us pain!)
  • Is it enough of a priority? For example, an inventory loss bug that affects many Residents gets a much higher priority than a cosmetic glitch only noticed by a few.
  • What are the dependencies? Second Life is a complex system and we need to be sure, even if a bug seems simple, that fixing it won't create more bugs in related areas.

For more background, see this.

How do I find out where bugs get fixed?

Search the Bug Tracker, or if you find that tricky, check the Release Notes. Each version contains blow-by-blow highlights of what was changed.

Want to know more?

After you've learned the essentials of bug reporting, give it some time to digest. Then: