1. Mantis Bug Tracker

2. MantisBT features Open source web-based bug tracking system. Track software defects. Mantis is often configured by users to serve as a more generic issue tracking system. Project management tool. E-mail notifications Modular Architecture

3. Features Mantis supports the sending of e-mail notifications upon changes being made to the system. Users have the ability to specify the type of e-mails they receive and set filters to define the minimum severity of issues to receive notifications about.

4. Requirements Mantis requires a configured web server, PHP programming language interpreter and relational database management system supported by ADOdb.

5. RequireMent WebServer – APACHE, Windows IIS DataBase -- Mysql, Postgresql, Mssql, DB2 PHP -- 5.2 or above OS -- Linux, Windows License -- GPL

6. Download Website link:  wget http://sourceforge.net/projects/mantisbt/files/mantis- stable/1.1.8/mantisbt-1.1.8.tar.gz/download

7. Deploy Mantis Mantis Installation:  cd /var/www/html  tar xvzf /root/mantisbt-1.1.8.tar.gz  mv mantisbt-1.1.8 mantis  cd mantis  cp config_inc.php.sample config_inc.php

8. Database Configure Mantis Database:  create database bugtracker  grant all on bugtracker.* to 'bugtracker'@'localhost' identified by 'bugtracker';

9. Mantis Access mantis by URL:  http://localhost/mantis http://localhost/mantis  http://ip-address/mantis

10. Mantis Default username & password  administrato r/root

11. Mantis Self Service Scenario  Create user  Change Password  Lost password

13. Access Level The default access levels shipped with MantisBT out of the box are:  VIEWER  REPORTER  UPDATER  DEVELOPER  MANAGER  ADMINISTRATOR Note that project specific access levels override the global access levels.

14. Create User  Click "Manage" on Main Menu.  Click "Manage Users" (if not selected by default).  Click "Create New Account" button just below the alphabet key.  Enter user name, email address, global access level (more details about access levels later). Other fields are optional.  Click "Create Users".  The user will receive an email allowing them to activate their account and set their password.

15. Issue Statuses  New  Acknowledged  Confirmed  Assigned  Resolved  Closed

16. Best Practices * Only testers are allowed to create issues. * Developers must send e - mail a tester to have them create an issue. * Developers send e - mail to technical lead for having him assign an issue to themselves for issues they think they can resolve. * A developer cannot assign an issue to another developer (Must send e - mail to technical lead). * If a developer's issue is blocked by another developer's code, she must solve this problem outside of the bug tracking system. * Only testers are allowed to close issues which are opened by themselves. * All assignments must go through technical lead so he can track issues. * Testers/QAEs are responsible for assigning a Severity to the bug i.e., Critical/Major/Minor etc. * Bugs that are not directly related to user interface are not entered into the system (must be resolved externally).

17. Addons More addons:  SVN with Mantisbt  Mediawiki with Mantisbt

18. Problem Problem with change log / roadmap.  http://www.mantisbt.org/bugs/view.php?id=10873