MantisBT

-



Bug Tracking with MantisBT

MantisBT is an open-source, web-based bug tracker that provides a delicate balance between simplicity and power. Users are able to get started in minutes and start managing their projects while collaborating with their teammates and clients effectively.
The name Mantis and the logo of the project refer to the Mantidae family of insects, known for the tracking of and feeding on other insects, colloquially referred to as "bugs". The name of the project is typically abbreviated to either MantisBT or just Mantis.

Installation

  • You must download the archive containing MantisBT. Unpack the archive in the web directory of your web server (eg / var/www)
  • Go to this page via your web browser to continue the installation:
  • Put the values shown in figure 1 and click on install/upgrade database.
  • Mantis is now installed.
  • You can use the following URL: https://www.mantisbt.org/

§  Default Username: administrator
§  Default  Password: root


figure 1



Configuration

          Configure Mantis

§  Configuring mantis is done through the config_inc.php configuration file.
§  The file contains the following lines:


Configure MySQL

 Configure MySQL to create a database and an authorised user on this database. In our case, the database is called "manrisdb" and the username "mantis"

Creating the database
Connect to the MySQL console:
create database mantisdb;
Creating the user account
grant all on mantisdb.* to 'mantis'@'localhost' identified by 'password';


Usage

Create users:-
  • Click "Manage" on Main Menu.
  • Click "Manage Users" (if not selected by default).
  • Click "Create New Account" button just below the alphabet key.
  • Enter username, email address, global access level (more details about access levels later). Other fields are optional.
  • Click "Create Users".



Create issues:-
  • Click "Report Issue" on Main Menu.
  •  Enter Category, Reproducibility, Priority, Assign To, Summary, Description, Attach Tags
  • Can upload attachments regarding the issue
  • Click "Submit Issue".




Handle issues:-
  • Update Issue - brings up a page to edit all aspects of the issue
  • Assign to - in conjunction with the drop-down list next top the button, this is a shortcut to change the assignment of an issue
  • Change Status to - in conjunction with the drop-down list next top the button, this is a shortcut to change the status of an issue. Another page (Change Status) will be presented to allow the user to add notes or change relevant information
  • Monitor / Unmonitored Issue - allows the user to monitor any additions to the issue by email
  •  Create Clone - create a copy of the current issue. This presents the user with a new issue reporting form with all of the information in the current issue filled in. Upon submission, a new issue, related to the current issue, will be created.
  • Reopen Issue - Allows the user to re-open a resolved issue
  • Move Issue - allows the user to move the issue to another project
  •  Delete Issue - Allows the user to delete the issue permanently. It is recommended against deleting issues unless the entry is frivolous.


Status:-
  • New - This is the landing status for new issues. Issues stay in this status until they are assigned, acknowledged, confirmed or resolved. The next status can be "acknowledged", "confirmed", "assigned" or "resolved".
  • Acknowledged - This status is used by the development team to reflect their agreement to the suggested feature request. Or to agree with what the reporter is suggesting in an issue report, although they didn’t yet attempt to reproduce what the reporter is referring to. The next status is typically "assigned" or "confirmed".
  • Confirmed - This status is typically used by the development team to mention that they agree with what the reporter is suggesting in the issue and that they have confirmed and reproduced the issue. The next status is typically "assigned".
  •  Assigned - This status is used to reflect that the issue has been assigned to one of the team members and that such team member is actively working on the issue. The next status is typically "resolved".
  • Resolved - This status is used to reflect that the issue has been resolved. An issue can be resolved with one of many resolutions (customizable). For example, an issue can be resolved as "fixed", "duplicate", "won’t fix", "no change required", etc. The next statuses are typically "closed" or in the case of the issue being re-opened, then it would be "feedback".
  • Closed - This status reflects that the issue is completely closed and no further actions are required on it. It also typically hides the issue from the View Issues page. Some teams use "closed" to reflect sign-off by the reporter and others use it to reflect the fact that the fix has been released to customers.


Email Notification:-

This page sets the system defaults for sending emails on issue related events. MantisBT uses flags and a threshold system to generate emails on events.
For each new event, email is sent to:

·         The reporter
·         The handler (or Assigned to)
·         Anyone monitoring the issue
·         Anyone who has ever added an issue notes the issue
·         Anyone assigned to the project whose access level matches a range


Advantages

·         Open source and web based
·         Easy to install
·         Simple user experience(Simple user interfaces that easy to understand)
·          Supports any platform that runs PHP (Windows, Linux, Mac, Solaris, AS400/i5, etc)
·         Multiple Projects per instance
·         Built-in Reporting (reports / graphs)
·         Users can have a different access level per project
·         Users can monitor specific issues
·         Group Actions: actions can be applied to multiple issues
·         Ability to view recently visited issues
·         Reporting issues via Email
·         Attachment Auto-Preview
·         Support for mobile devices


Disadvantages

·         Some basic features, such as searching, aren’t available for custom fields.

Reference
1.      https://www.mantisbt.org/
2.      https://www.mantisbt.org/wiki/doku.php
3.      https://www.mantisbt.org/docs/master-1.2.x/en/administration_guide.pdf

4.      https://en.wikipedia.org/wiki/Mantis_Bug_Tracker

Comments

Post a Comment

Popular posts from this blog

CSRF Token-Synchronizer Token Patterns

-
Image
Cross-site Request Forgery Protection in web applications via Synchronizer Token Patterns What is Cross-site Request Forgery Protection(CSRF)? This is a kind of attack and type of a malicious exploit of a website. We also name this attack as the one-click attack or session riding. This forces an end user to execute unwanted actions on a web application in which they're currently authenticated. This attack is mainly focusing on state-changing request, not theft data. As an example, if the user 'A' wants to transfer the 200$ to the bank 'B'.He needs to send a request to the bank 'B' and bank will send the response by authenticating user 'A'.There is an attacker he/she needs to fraud this money form user 'A'.what the attacker can do is he will create a malicious web link and send it to the user by forcing to click that link . while the user clicks the link for the transferring purpose but the thing is attacker was transferring the mon...
Read more

CSRF token - Double Submit Cookies Pattern

-
Image
Cross-site Request Forgery Protection in web applications via  Double Submit Cookies Pattern What is Cross-site Request Forgery Protection(CSRF)? This is a kind of attack and type of a malicious exploit of a website. We also name this attack as the one-click attack or session riding. This forces an end user to execute unwanted actions on a web application in which they're currently authenticated. This attack is mainly focusing on state-changing request, not theft data. As an example, if the user 'A' wants to transfer the 200$ to the bank 'B'.He needs to send a request to the bank 'B' and bank will send the response by authenticating user 'A'.There is an attacker he/she needs to fraud this money form user 'A'.what the attacker can do is he will create a malicious web link and send it to the user by forcing to click that link . while the user clicks the link for the transferring purpose but the thing is attacker was transferring th...
Read more

Cloud Computing

-
Image
Cloud Computing What is Cloud Computing In the simplest terms, cloud computing means storing and accessing data and programs over the Internet instead of your computer's hard drive. The cloud is just a metaphor for the Internet. It goes back to the days of flowcharts and presentations that would represent the gigantic server-farm infrastructure of the Internet as nothing but a puffy, white cumulus cloud, accepting connections and doling out information as it floats. Usage of Cloud Computing 1. Infrastructure as a service (IaaS) and platform as a service (PaaS)   When it comes to IaaS, using an existing infrastructure on a pay-per-use scheme seems to be an obvious choice for companies saving on the cost of investing to acquire, manage and maintain an IT infrastructure. There are also instances where organizations turn to PaaS for the same reasons while also seeking to increase the speed of development on a ready-to-use platform to deploy applications. 2. Priva...
Read more