Difference between revisions of "Bug Tracker/Details"

From Second Life Wiki
Jump to navigation Jump to search
(Created page with '=== Determine if the issue has already been submitted === Before reporting issues of widespread system breakage, you should first see if there is any existing information by sear...')
 
m (moved Issue Tracker/Details to Bug Tracker/Details: http://blogs.secondlife.com/community/technology/blog/2010/09/07/introducing-the-new-jira)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Determine if the issue has already been submitted ===
To report a new bug, do the following:
Before reporting issues of widespread system breakage, you should first see if there is any existing information by searching the [http://secondlife.com/community/support.php support resources], and look for the latest status reports on the [http://status.secondlifegrid.net/ Status Reports page].
 
Avoiding duplicate issues is very important.  Sorting through duplicates wastes time and effort (for both Linden Lab staff and fellow residents), and it causes bugs and feature proposals to seem like they are getting less attention than they actually are.  It is more effective to concentrate efforts about the same problem in the same reported issue, especially since more-active issues receive greater priority.
 
After logging in, you will see the Dashboard. Here you have access to some search filters which give you access to the most up-to-date information on submitted issues. For example, you can click on ones which show all unresolved issues within each project, then begin a text search from there (by editing the filter). Of course you may simply run a new search from the '''Quick Search:''' box. Either way, it is best practice to search for issues you wish to report in several ways before submitting them!
 
::If you find that your issue was already submitted, you can still do several things to help:
::* Leave a comment containing additional information or details
::* If it's a bug, possibly explain another way to reproduce the bug
::* Vote for the issue to express that you feel it is important.
::The more good, SPECIFIC information there is about an issue, the better chance it has for a quick resolution.
 
=== To submit a bug ===
To create a new bug, do the following:
# Click the "Create New Issue" link in the blue navigation bar towards the top of the screen.  (If you don't see this, make sure you are [[Issue_tracker/FAQ#How_do_I_log_in_to_the_Tracker.3F|logged in to JIRA]].)
# Click the "Create New Issue" link in the blue navigation bar towards the top of the screen.  (If you don't see this, make sure you are [[Issue_tracker/FAQ#How_do_I_log_in_to_the_Tracker.3F|logged in to JIRA]].)
# On the first page:
# On the first page:

Latest revision as of 08:37, 8 September 2010

To report a new bug, do the following:

  1. Click the "Create New Issue" link in the blue navigation bar towards the top of the screen. (If you don't see this, make sure you are logged in to JIRA.)
  2. On the first page:
    • Select a Project that most closely matches the kind of bug you are submitting - see Projects and Components.
    • Select "Bug" as your Issue type.
    • Click "Next".
  3. On the second page:
    1. Enter a concise but informative summary (title) for the issue
    2. Select the priority (severity) of the bug. For example, a "Showstopper" bug might render the program useless, but a "small" bug might be merely cosmetic. Click the Help icon next to the dropdown for more details.
    3. Select components that narrow the scope of the bug. You can select multiple components by Ctrl-clicking.
    4. Choose the versions that the bug effects. You should only select those versions where you have observed the bug, and only select a "First Look" version if the bug only applies to First Look.
    5. Describe the computer environment in which the problem occured. For example, if you have noticed that the bug only occurs with certain hardware or software configurations.
      • The best way to report this information is to paste the info that comes from inside Second Life viewer. (Help menu > About Second Life...) Certain facts might be relevant (Windows vs Mac vs Linux machine, or graphics card model, or headset models for voice features). If configuration truly doesn't matter, you can leave it blank.
      • For example, "Only happens with Mac OS X 10.4.1," or "Seen only with NVIDIA GeForce Go 7800 card," etc.
    6. Enter a detailed description of the issue, and be sure to include:
      • Steps (1,2,3...) to reliably reproduce the bug-- How to make the bug happen. If you cannot identify the specific steps, describe what seems to lead to the bug. Try to make this as simple as possible while still being specific enough to reproduce the bug. Simpler reproductions make it easier to narrow down the causes.
      • OBSERVED results (what happens when the bug occurs)
      • EXPECTED results (what behavior you would have expected instead)
      • As a reminder: be as detailed as possible without including personal information!
    7. If you have a screenshot or video of the bug, or any other relevant file, you can attach it under attachment. Note that it has a 10MB size limit per file. You can also attach additional files later. (See Debug Help for various ways to hunt for such additional information.)
    8. If you are a programmer and are attaching a patch for the source code, enter the source version the patch is against and check the patch attached box.
  4. Finally, click "Create" to create the new issue.
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Bug_Tracker/Details&oldid=1029142"