Using Mantis (Sanctum Bug List)
NIOGA's Sanctum Bug
List uses Mantis, an open-source bug tracker. This page gives
you a quick introduction.
Click the "Bug List" link now to open Mantis in a new browser window.
- Logging Into Mantis
- Changing Your Mantis Password
- View Bugs page
- Bug Description pages
1. Logging Into Mantis
The first time you use Mantis, you'll see the Mantis login page.
- Click the "signup for a new account"
link.
- Enter a username and your e-mail address.
- A random password will be e-mailed to you. (You'll change it in the next
step.)
- When you receive your password, log in.
- If you're on a private computer, and your browser has cookies enabled, you
can check the "Save Login" box.
All Beta Reward points you earn will go to your username.
If you're just visiting, you can log in using Username "Rev1",
Password "revs".
2. Changing Your Mantis Password
- On the Mantis main page, click the "My Account"
link.
- Change your password as desired, then click "Update User".
3. View Bugs page
Click the "View Bugs" link to see all
current bug entries.
- You may wish to check the "Hide Status: Closed" box in the upper
right corner.
- Then click "Apply Filter".
- This hides all "closed" entries, so they don't clutter the table.
All open bug entries are shown in the table. The most important columns are:
|
ID
|
Status
|
Summary |
|
The bug's ID number.
|
'feedback' means you can test it.
|
A brief description of the bug. |
The ID number is also a link. Click it to go to the
bug's detailed description page. |
Anything else means don't test it.
- 'new' means it's not fixed yet.
- 'acknowledged' means fixed, but not yet available.
|
|
Click on the column headers to sort the whole table by that column.
- Your job as a Beta tester is to test all 'feedback' entries, and report
on them.
4. Bug Description pages
Click on a bug's ID link to go to its Bug Description page. Every bug entry
has its own Bug Description page.
- Read the "Summary" and "Description" sections to understand
the bug.
- Scroll down to the bottom of the page and read the "Bug Notes"
for this bug. This may give some additional details about the fix.
To test a bug:
- Generally, you just repeat the situation as described in the Description,
and see if the bug still happens.
- If the bug does not happen, that confirms the fix.
- The "Steps to Reproduce" may have detailed instructions for duplicating
the bug. (Easy bugs skip this.)
- The "Bug Notes" may also have more information.