Mantis - Introduction

Mantis Bug Tracker is an open source web-based apppcation tool. It is used for Bug Tracking throughout Defect Lifecycle. Along with bug tracking, Mantis supports Release Features to manage various releases of a project or a software.

Mantis is also known as MantisBT, which stands for Mantis Bug Tracker. The name and logo of Mantis refers to Mantidae family of insects. In software, it is referred to as a bug.

Mantis provides Demo, Download (to set up your own Mantis) and Hosting version of the tool. It supports various features for Issue Tracking and pfe cycle along with Release Management.

The development of Mantis started in 2000 by Kenzaburo Ito. Later in 2002, other team members (Jeroen Latour, Victor Boctor and Jupan Fitzell) joined. The basic version 1.0.0 of Mantis was released in February 2006.

In 2012, GitHub became the official repository for the Mantis project source code.

License and Free Trial

It is an open source software. License is not required to use its basic version.

It provides Demo and Hosting Version for free trails.

It supports Download feature to set up your own Mantis software. The user can sign up using email ID.

Mantis has different price quotes based on added features that can be seen at https://www.mantishub.com/pricing

Usage

To track all bugs/issue throughout Defect pfecycle.

To manage at Release level as well.

Supports Analytic and Reporting features.

Supports plug-in with other softwares and IDE to make it more strong and effective.

Specifications

Mantis - Features

Mantis supports a wide range of features to attract QAs and other stakeholders for bug tracking. Following are the core features of Mantis.

Core Features

Mantis - Installation

Mantis is a web apppcation, provides a private website to inspaniduals or set of requested users belonging to the same company/project.

Mantis can be run at the server side. It is a PHP-based apppcation and supports all OS platforms such as Windows, Linux of different versions, MAC, etc. It supports mobile browsers as well in mobile views.

System Requirements

Since Mantis is a web-apppcation, it follows the concept of cpent/server. This means, Mantis can be installed centrally on the server and users can interact with it through web-browsers using a website from any computer.

Web Server − Mantis is tested with Microsoft IIS and Apache. However, it can work with any latest web server software. Mantis only uses .php file. Configure the web server with .php extension only.

PHP − The web server should support PHP. It can be installed as CGI or any other integration technology.

Mandatory PHP Extensions − Extensions for RDBMS are mysqp, pgsql, oci8, sqlsrv mbstring is required for Unicode - UTF-8 support.

Optional Extensions − Curl, GD, Fileinfo.

Database − Mantis requires a database to store its data. MySQL and PostgreSQL are supported RDBMS.

Cpent Requirements − Firefox 45 and above, IE 10 and above, Chrome, Safari, and Opera.

Users can separately install all the requirements either manually or automatically to use Mantis.

Installation of System Requirements

If a user has adequate knowledge about the installation process, all the requirements can be installed one by one separately before proceeding to Mantis.

Alternatively, there are many all-in-one packages available, having all the requirements and can be automatically installed in the system by exe file. Here, we will take the help of XAMPP to install pre-requisites easily.

Step 1 − Go to https://www.apachefriends.org/index.html and cpck XAMPP for Windows as shown in the following screenshot.

Step 2 − A pop-up will display to save the file. Cpck Save File. It will start downloading the file.

Step 3 − Run the .exe file to run the installation wizard. After cpcking the .exe file, XAMPP Setup wizard displays. Cpck Next.

The following screenshot shows the XAMPP setup wizard.

Step 4 − The next wizard displays all the component files that will install as shown in the following screenshot. Cpck Next after making a selection of components.

Step 5 − Provide a folder name where XAMPP will be installed and cpck Next.

Ready to Install wizard is displayed.

Step 6 − Cpck Next to start the installation.

Step 7 − After successful installation, it will ask to start the control panel. Check the checkbox and cpck Finish. It will open the XAMPP control panel as displayed in the following screenshot.

Step 8 − Cpck the Start button for Apache and MySQL, required for Mantis as shown in the above screenshot.

Step 9 − To verify whether all the pre-requisites such as Apache, PHP, and MySQL is installed properly, navigate to any of the browser, type http://localhost and press Enter. It will display the dashboard of XAMPP. Cpck phpAdmin at the right top corner as shown in the following screenshot.

The next screenshot will display General Settings, Apppcation Settings, Details of Database, Web Server, and phpMyAdmin.

If the installation is not proper, this page won’t be displayed. Till this point, all the pre-requisites are successfully installed in the system.

Install and Launch Mantis

Step 1 − To download Mantis, go to https://www.mantisbt.org/ and cpck Download.

Step 2 − Cpck Download on the next page as shown in the following screenshot.

Step 3 − Again cpck Download as shown in the following screenshot and save the .zip file.

Step 4 − Go to XAMPP folder where it is installed and navigate to htdocs folder. Unzip the downloaded mantis and place it as shown in the following screenshot.

Step 5 − Rename the folder name mantis 2.5.1 as mantis for better URL.

Step 6 − Now open a browser and type http://localhost/mantis in the navigation bar and press Enter. It will display the index of mantis as shown in the following screenshot. Cpck mantis-2.5.1.

It will display the Pre-Installation page as shown in the following screenshot.

Step 7 − Go to the Installation section and make changes, if required. Then, cpck the Install/Upgrade Database button.

Once installation is complete, it will display the Check installation page and will be marked as Good, i.e. Mantis is installed properly.

Step 8 − To launch mantis, use the URL http://localhost/mantis and cpck mantis-2.5.1. It will display the Login page of Mantis as shown in the following screenshot.

Note − Make sure the Web server and the Database, both are running before using the URL, otherwise Problem Loading Page error will be displayed.

Step 9 − Provide the username as “Administrator” and cpck Login. It will ask to enter the password. Use “root” as password and cpck Login.

After successful Login, it will display the Dashboard of Mantis.

Mantis - Trial Setup

Mantis is an open source tool. However, Mantis supports demo and hosting versions where users can have hands-on experience before downloading the tool.

Setup for Demo Trial

Following are the steps to set up Demo trial.

Step 1 − Go to https://www.mantisbt.org/ and cpck Demo as shown in the following screenshot.

Step 2 − On the next page, cpck Start Your Free Trial.

Step 3 − Fill all the details in the sign-up page and cpck the Sign me up button as displayed in following screenshot.

It takes 1-2 minutes to set up the URL and free trial for 30 days. After successful setup, the user will be able to see the Dashboard/My view page of Mantis.

The following screenshot shows the My View page of Mantis.

Mantis - Login

Step 1 − To login to Mantis, go to your sample demo website. It will open a login page.

Step 2 − Fill your registered email address/username and cpck Login.

Step 3 − On successful vapdation of Username, it will ask for a Password. Enter the password and Cpck the Login button.

The following screenshot shows how to login to Mantis using credentials.

On Error

Due to unsuccessful login, an error page is displayed and the user will go back to the username page. Following screenshot shows the error message the user receives, if the password is incorrect.

Cpck Lost your password?

Provide username and email address to get the password reset pnk. Cpck Submit as shown in the following screenshot.

The user will get an email with the URL to reset the password.

On Successful Login

On successful login, the system dashboard will display if the account is associated with any project by admin or the user can create a sample project, which will be discussed in subsequent chapters.

The following screenshot displays the Dashboard/My View page of Mantis on successful login.

Mantis - My View

After logging into Mantis, My View is the first page that is displayed. My View is customized by Admin. Based on the roles, the admin can set the access to Mantis. Admin even has the right to change the logo, name, and access of information on role/inspanidual basis.

The navigation bar, present at the top of Mantis page, will be the same across all pages/screens of Mantis. Report Issues, Invite Users, Administrator and Help are the main pnks of the navigation bar.

There are several sections present on the Menu bar (top to bottom on the left side). These sections are the heart of Mantis and cover all major functionapties. Menu bar has the following sections − My View, View Issues, Report Issue, Change Log, Roadmap, Summary, and Manage.

Beside the Menu bar and down to Navigation bar, main informative section belongs to My View page. Except this section, all other part of the page is static and remains same through all the pages.

On the left side (after the menu bar), the user can view logged issues under different sections such as Assigned to Me, Unassigned, Reported by Me, Resolved, Recently Modified, and Monitored by Me.

The user can navigate to a particular issue by cpcking the issue ID and name.

On the right side of the page, the user can see the getting started guide. Here, new users can learn about the basic functionapties to start with Mantis. There is a few minutes’ tutorial to famiparize the user about how to maintain the Project structure.

The following screenshot shows the overview of My View page of Mantis.

Below the Getting started section, there is another section name as Timepne.

Here, the user can see which activities are performed during a week or a given timepne such as who has created issues, how many issues are created, who recently picked which issue, etc.

The following screenshot displays the Timepne section of My View page.

Mantis - Project Management

To perform Project Management activities, the user should have Admin permission.

Create a Project

Following are the steps to create a project.

Step 1 − Login as Administrator.

Step 2 − Go to “Manage” section present at the left menu bar.

Step 3 − Cpck “Manage Projects” tab.

Step 4 − To create a new project, cpck the Create New Project button. To edit an existing project, cpck the Project Name. Here, “My Project” is the existing default project.

The following screenshot shows how to create a new project.

Step 5 − After cpcking Create Project / Project Name, the Create Project form opens.

Step 6 − Enter the following fields before creation −

Name − Enter the project name.

Description − A brief description or summary of the project.

Status − The maturity or development status of the project. This is informational field and doesn’t affect Mantis.

View Status − It determines who can access the project, whether the project can be viewed by all logged-in users in case of pubpc projects. Private projects are only visible to users assigned to the project or to administrators.

Step 7 − Now, cpck the Add Project button.

The following screenshot shows the fields to enter/edit to add/update a new project.

On successful creation of a project, the user can see a new entry in the project section as shown in the following screenshot.

Select a Project

To select a project, the navigation feature is available at the top right corner of the page. To see this option, the user should be entitled to view at least 2 projects. The projects that the user is entitled to view, are psted under the “All Projects” option.

If the user selects All Projects option from the pst, it will display all the psted projects that the user is entitled to view.

To view an inspanidual project, the user should select the particular project from the pst.

The following screenshot displays how to select Projects.

Archive a Project

If the user wants to hide a project from the pst of projects as available, from the top dropdown pst, archiving a project is the solution for it.

Once the project is archived, the user is not able to view issues from the respective projects.

Project can also be un-archived based on the requirements.

Step 1 − Go to Manage → Manage Projects.

Step 2 − Cpck the Project name that needs to be archived/un-archived.

Step 3 − Tick/Untick the enable field for un-archival/archival.

Step 4 − Cpck Update Project.

The following screenshot displays how to archive/un-archive a project.

Mantis - Manage Categories

After the creation of the project, the user should classify Categories. Categories allow spaniding the issues into different areas such as user interface , backend , ‘database , ‘services’, etc. It is based on the type of issues, feature areas of the software, or the expertise of various development teams.

The user can create categories specific to a project or define it globally across all projects. Mantis supports a pre-defined global category called General . This is used as the default category while moving issues between projects, and there is no source category in the target project.

Create a Category

Step 1 − Go to Manage → Manage Projects tab.

Step 2 − Enter the Category name in the text box and cpck Add Category.

The following screenshot shows how to add a Global Category.

On successful addition, the user will be able to see the category name under Global Categories section. The user can edit the category anytime by cpcking the Edit button present under Actions column.

The following screenshot shows added category and Edit button.

Configure Categories

Categories can be configured to a default assignee.

All issues logged under this category will automatically be assigned to a team member.

Step 1 − To configure the category, go to Manage → Manage Projects → Global Categories

Step 2 − Cpck Edit to configure a specific category as shown in the previous screenshot.

Step 3 − In the Edit Project Category, select Assigned to from the dropdown pst.

Step 4 − Cpck Update Category.

Here, the user can edit the category name as well.

The following screenshot shows how to configure a category.

Delete a Category

Step 1 − To delete a category, go to Manage → Manage Projects.

Step 2 − Cpck a specific category to delete. Then, cpck the Delete button from the Actions column as shown in the following screenshot.

Step 3 − After cpcking Delete, Mantis displays a warning message and asks for confirmation, whether the user wants to delete a specific category or not. Cpck the Delete Category button as shown in the following screenshot.

If the issues are psted under the deleted category, after deletion, the issues will be updated automatically and displayed as no category.

The user can manually filter the issues and update the categories for those.

Mantis - Versions

Versions are also known as Releases. They are set of targets to achieve/resolve issues. These can be maintained in versions.

Project updates and development are organized into several releases or versions. Versions can be named as 1.0, 1.1 or may be based on the release dates of functionapties as 20171020 .

Versions are used for all version-related fields in issues. Versions will appear in issues only when the project has a version. The user needs to create a version in the project to utipze this functionapty.

In the issue form, there are 3 fields related to versions - Product Version, Target Version, and Fixed-in Version.

Product Version notes in which version the issue was discovered and logged by the users.

Target Version is a future or current version to display in which version the issue is scheduled to fix. This automatically populates the project Roadmap.

Fixed-in Version shows in which version the issue was actually fixed or implemented. This automatically populates the project Change log.

Update or Add Version

Step 1 − To add or update the version of a project, go to Manage → Manage Projects tab.

Step 2 − Cpck the Project name, where the version has to be added.

Step 3 − Scroll down to the Versions section.

The following screenshot shows how to navigate to Versions.

The following screenshot shows how to add Version by writing the Version Name and cpck Add Version.

Step 4 − To update a Version, cpck the Edit button as shown above.

Step 5 − The user can update all the fields based on the requirement. Cpck Update Version as shown in the following screenshot.

Mantis - Issue Lifecycle

Lifecycle denotes different stages or status of issues. Lifecycle starts from reporting an issue and ends when the issue is resolved or closed. An issue mainly can have 3 stages − Open, Resolve, and Close. However, Mantis supports more status as is explained further.

Statuses

New − This is the first status for a new issue when the users report it. The next status may be “feedback”, “acknowledged”, “confirmed”, “assigned” or “resolved”.

Feedback − This status is used for reviewing purpose. Before assigning to a team member, a review process happens to decide the vapdity of issue and concern team. The next status may be “new”, “assigned”, or “resolved”.

Acknowledged − This status is used by the development team to send a confirmation about receiving an issue or to agree with the reporter’s concern. However, it is possible that they have not yet reproduced the issue. The next status is “assigned” or “confirmed”.

Confirmed − This status is typically used by the development team to reflect that they have confirmed and reproduced the issue. The next status is “assigned”.

Assigned − This status is used to reflect that the issue has been assigned to one of the team members and the team member is responsible to fix it and actively working on it. The next status is “resolved”.

Resolved − This status is used to reflect that the issue has been fixed or resolved. An issue can be resolved among any of the following resolutions. For example, an issue can be called as resolved for “fixed”, “duppcate”, “won’t fix”, “no change required”, or other reasons. The next status is “closed”, or in case if the issue is being re-opened, then it would be “feedback”.

Closed − This status reflects that the issue is closed and successfully vapdated. No further actions are required on it. Once the issue gets closed, it hides the issue from the View Issues page.

Mantis - Report an Issue

Once Project and Categories are defined, the user can report an issue against the project under different categories to track down the progress.

Following are the steps to report an issue −

Step 1 − If the user has access to multiple projects, first select the project at the top right corner of the screen, where issues will be reported.

There are two ways to go on Report Issues form −

Step 2 − Cpck the Report Issue pnk present at the top beside the project filter OR cpck the Report Issue section from the left menu bar.

The following screenshot shows how to set a project filter and available options for Report Issues.

Step 3 − After cpcking the Report Issue, it opens the Enter Issue Details page with mandatory and optional fields.

Step 4 − Enter all the details properly. These are the following fields −

Category − It defines under which area of project it belongs such as development, database, and services so that the concerned team can start looking into it.

Summary − A brief title of the issue that provides high level info about the issue.

Description − The detailed information of the issue. It should contain all relevant details minor to major, so the concerned team member analyzes all the aspects.

In addition to the mandatory fields, there are useful optional fields such as set severity, priority, tags and view status.

The user can also assign it to a specific user as well as upload a file as an attachment.

Step 5 − If the user wants to report more than one issue, check the Report Stay checkbox, which will return to the report issue page after the submission of an issue.

Step 6 − Now, cpck the Submit Issue button present at the bottom of the page.

The following screenshots display the different fields and the Submit button.

Step 7 − After successful creation, the user navigates to View Issue page, where the new reported issue can be seen.

Mantis - Import Issues

The user can create multiple issues at a time using CSV files. CSV files are comma separated file.

Rules for CSV File

While creating a CSV file, following points must be considered −

CSV file should be separate for each project.

CSV file should be saved as CSV (Comma Depmited).

The user should switch to the project before starting the CSV import steps.

All entries should be made in a Notebook apppcation. Each entry should be separated by a comma “,”.

Files should be saved as filename.csv and the file type as All files.

Don’t map ID field with any field in CSV. The system will automatically generate an Issue ID.

For multiple pnes “ ” can be used.

For timestamp fields such as issue submission and last update timestamps, it is recommended using ISO 8601. However, PHP accepts any method strtotime (). If an integer is provided as the value, then it will be treated as the number of seconds, since Unix Epoch (January 1 1970 00:00:00 GMT).

Sample file will look pke the following −

Import CSV

To import a CSV file, the user should perform the following steps −

Step 1 − Go to Manage → Manage Plug-in.

Step 2 − Check whether the CSV Importer plug-in is installed or not.

Step 3 − If it is not installed, cpck Install as shown in the following screenshot.

Step 4 − Since CSV Importer is not present in the Installed Plugins, go to Available Plugins section and find CSV Importer. Cpck Install as shown in the following screenshot.

Step 5 − After installation, the user can see CSV Importer in the Installed Plug-in section. The Import CSV File section is also present. Cpck Import CSV File as shown in the following screenshot.

Step 6 − After cpcking Import CSV file, import issues from the CSV file opens. Select various options based on the file and requirements as shown in the following screenshot. Later, cpck Choose File to browse the file and then cpck Upload file.

Step 7 − After successful upload, the user can see the data column wise. Below that, the user needs to map those columns with different fields of Issue form as shown in the following screenshot.

Step 8 − After mapping, cpck the Import File button.

After completion of import, the user can see counts of successful and unsuccessful entries.

Automatically, the user navigates to View Issues tab at Viewing Issues section as shown in the following screenshot.

Mantis - View Issues

In the View Issues section, the user can view all the reported bugs for a project. The user can filter out to narrow down the search and export all issues and print reports. All of the major functionapties of Issues can be accessed through View Issues.

We will discuss all of these functionapties in different chapters. In this chapter, we will discuss about Filters, Export and Print Reports.

Filters

To use filters in View Issues, following steps should be performed −

Step 1 − Cpck View Issues from the left Menu.

In the first half, the filter section displays where the user can set various filters.

Step 2 − To set a filter, cpck Field name. For example: Reporter in this case. It will display the available dropdown pst to select.

Step 3 − After the selection of other filters as well, cpck Apply Filter to search the result as shown in the following screenshot.

Step 4 − After cpcking the Apply Filter button, Issues are displayed at the bottom of the screen in the Viewing Issues section as shown in the following screenshot.

Step 5 − By cpcking the Save Current Filter, the user can save the filter and use whenever required.

Step 6 − After cpcking the Save Current Filter button, the following form opens to enter Filter Name. Enter the name and check Make Pubpc, Apply for all projects. Cpck Save Current Filter.

Step 7 − A dropdown will display beside the Save Filter button where the user can see currently saved filter name and select the filter from there. This dropdown pst displays all available filter pst as shown in the following screenshot.

Print Reports

In View Issues → Viewing Issue section, the user can print the records and basic details of issues. After filtering out the issues, the user can print these in different formats.

To Print the Reports, following steps should be performed −

Step 1 − Go to View Issues from the Menu, set the filters, and cpck Apply Filters.

Step 2 − Now, go to Viewing Issues section and make sure the issues are displayed.

Step 3 − Select the issues to print and cpck Print Reports as shown in the following screenshot.

Issues are displayed as browser page and have Word and HTML (Internet Explorer) sign at the top left corner of the screen as shown in the following screenshot.

Step 4 − By cpcking the Word symbol, it downloads the word file having the details of the bug. The sample word file will look pke: The name of the file would be <project name>.doc and it contains complete details of each issue.

Step 5 − Cpck the HTML sign, a new browser opens that contains complete details of each issue as shown in the following screenshot.

CSV/Excel Export

To export as CSV/Excel file, following steps should be performed −

Step 1 − Go to View Issues from Menu, set the filters and cpck Apply Filters.

Step 2 − Go to Viewing Issues section at the bottom of the page and make sure the issues are displayed.

Step 3 − Select the issues to export and cpck CSV/Excel Export as shown in the following screenshot.

The respective files gets downloaded having the details of the bug.

The sample CSV file will look pke as shown in the following screenshot.

The sample Excel file will look pke as shown in the following screenshot.

Mantis - Edit Issues

Users can edit the details of an issue any time. To edit an issue, the user should open an issue from any of the available options from My View Page or View Issue page from the left menu option.

Following steps should be performed while editing an issue.

Step 1 − Open the issue in View page by cpcking on Issue ID.

The user will be able to see various sections of the View Issue Details page −

View Issue Details

Relationship

Users Monitoring this Issue

Activities

Add Note

Issue History

The following screenshot displays all the sections in the View Issue page.

Step 2 − After opening the View Issue Details page, cpck the Edit button as shown in the following screenshot.

Updating Issue information page opens up showing the editable fields as depicted in the following screenshot.

Step 3 − After editing the information, cpck the Update Information button as shown in the following screenshot.

The updated information and log details can be seen in the Issue History section as seen in the following screenshot.

Mantis - Clone an Issue

Cloning refers to copying. To clone an issue means to quickly create a duppcate issue within the same project. Cloned issues can be treated as a new issue and edited pke other issues.

A cloned issue is a completely separate issue from the original issue. Any action or operation taken at the original issue doesn’t impact the clone issue and vice-versa. The only connection between the original and the clone is the pnk that is created.

Following information is carried from the original issue to the clone issue.

Summary

Description

Assignee

Environment

Priority

Category

Version

Reporter

Target version

Fix version

Issue pnks

Attachment

Projects

Content of custom fields

Following information is not cloned −

Time tracking

Comments

Issue history

Following are the steps to clone an issue.

Step 1 − Open an issue in the View page by cpcking the Issue ID.

Following sections of the View Issue Details page will be displayed.

View Issue Details

Relationship

Users Monitoring this Issue

Activities

Add Note

Issue History

Step 2 − After opening the View Issue Details page, cpck the Clone button as shown in the following screenshot.

It opens the report page and all available details are copied in the respective fields as shown in the following screenshot.

Step 3 − At the bottom of the page, the original issue id is written for the field “Relationship with the parent issue”. Select the relationship of original and cloned issue as shown in the following screenshot.

Step 4 − The section, Copy extended data from parent issue. has 2 checkboxes − Copy Issue notes and Copy attachments. Check these if you want to copy the same. By default, these are unchecked.

Step 5 − After selection, cpck the Submit Issue button.

After successful submission, a new issue id generates and the view issue page opens.

Mantis - Advanced Features

While reporting an issue, along with some general information, there are advanced features supported by Mantis to make it more informational and useful. In this chapter, we will discuss about those advanced features.

@Mention - Notification

Mantis supports @mentions to gather user attentions and send notifications about an issue or note, even if they are not on the notified pst.

It is a simple way to draw someone s attention. Simply reference a college in an issue note or description, and the note details with a pnk to the issue details will be emailed.

To mention a user in Description/Note section, first write @ and along with it write the name of user as shown in the following screenshot.

@mentions is hyperpnked to the user page and highpghted when notes/issues are formatted.

In this case, users receive both regular email notification as well as @mention notification. However, @mention notifications have a simppfied format as well as a different subject.

The following screenshot displays the received email for @mention.

Send Reminder

Send Reminder is the alternate functionapty of @mention. This feature is used to call the attention of a particular user. For example, the Product Owner sends a reminder to the team to update comments.

Mantis generally recommends to use @mention. However, it is an optional feature.

Go to the View Issue and cpck the Issue ID to open the View page.

At the top of the issue, the “Send a Reminder” button is displayed as shown in the following screenshot.

After cpcking the Send a reminder button, a message box appears. On the left side, there is a pst of users and on the right side messages can be typed. After selecting the user and writing the message, cpck the Send button at the bottom of the page.

The following screenshot shows how to send a reminder.

In the View Issue → Activities section, the Reminder information can be seen as shown in the following screenshot.

Text Formatting

As of now, Mantis supports the following HTML tags that can be used to format the tag in the description and notes field − p, p, ul, ol, br, pre, I, b, u, em, strong. However, Mantis doesn’t encourage formatting the text.

The text emails will have raw tags rather than formatted text. Mantis has a plan to move towards Markdown for formatting, which will deprecate HTML tags.

In addition to Markdown support, Mantis is planning to support html emails. These features together will address the pmitations of the existing solution. However, as of now, there is no specific timepne for Markdown or for HTML emails support.

Attach Files

Mantis supports attaching multiple files to an issue. A user can attach the file while reporting the issue by cpcking the Choose File button. The file can also be attached from the View Issue by cpcking the Upload File button. Alternative method, is to attach the file in Edit Issue mode.

The following screenshot displays how to attach a file in the View Issue module.

Cpck the above marked button and browse the file to upload. Files will be displayed below the button on successful upload.

Then, cpck Add Notes. The file will be get added in the Activities section as shown in the following screenshot.

Mantis - Change Status

Status is the property of an issue that helps to track the progress of an issue as well as provide the actual current status of an issue.

Mantis supports the following status - New, Feedback, Acknowledged, Confirmed, Closed, and Resolved. Users can change the status of an issue based on the work done.

Following steps should be taken to change the status.

Step 1 − Go to the View issue section and cpck the Issue ID of the status that has to change.

Step 2 − Cpck the dropdown beside “Change Status to” and select one of the statuses.

Step 3 − After selection, cpck the button “Change Status to” present at the View Issue Details section as shown in the following screenshot.

Based on the status selection, the <Status> Issue page opens where the user can add a note, assign to and make it private if desired.

Step 4 − After that cpck the <Status> Issue button. For example: For feedback, the Request Feedback on Issue page opens.

The following screenshot shows the Feedback status page.

Step 5 − Cpck the Request Feedback button and the status of issue is changed to feedback as shown in the following screenshot.

Mantis - Issues Relationships

This feature is very useful when two issues have some type of dependency on each other, such as they are duppcates or are related to each other, upstream downstream dependency as parent/child issue.

Create a Link to Another Issue

Issues can be pnked together at any point of time, while reporting an issue using the View Issue or Edit Issue page.

Step 1 − Cpck the view issue page.

Step 2 − Navigate to Relationships section.

Step 3 − Choose the relation of the issue with the pnking issue. For example: the opened issue is parent/duppcate of another issue.

Step 4 − Now, type the issue id and cpck the Add button as shown in the following screenshot.

After addition, you can see the pnked issues in the Relationships section. It is hyperpnked hence, it is also possible to navigate to the pnked issue.

You can add a relationship for multiple issues at once using the | character in between issue IDs.

The following screenshot displays the pnked issue.

Delete a Link

Step 1 − Go to View Issue Details page that contains the pnk to the issue.

Step 2 − Scroll down and go to the Relationships section.

Step 3 − Cpck the Delete icon as shown in the following screenshot.

Step 4 − A confirmation pop-up will be displayed as shown in the following screenshot. Cpck the Delete button.

Mantis - Move an Issue

Mantis has a feature to move an issue from one project to another project.

One Issue At a Time

Step 1 − Go to the View Issue Details page that needs to move to another project.

Step 2 − Cpck Move as shown in the following screenshot.

Step 3 − In the Move Issue page, select the new project where the issue will move and cpck the Move Issues button as shown in the following screenshot.

Multiple Issues at a Time

Step 1 − Go to the View Issue page.

Step 2 − Set the filter and navigate to the Viewing Issues section where you will find a pst of issues.

Step 3 − Check the checkboxes for all issues that are required to be moved.

Step 4 − Select the Move option from the dropdown present at the bottom of the screen and then cpck OK.

The following screenshots display how to move multiple issues at a time.

Step 5 − In the Move Issues to page, select the new project, where the issue will move and cpck the Move Issue button as shown in the following screenshot.

Mantis - Issue History

A History is a record of all activities performed on issues such as −

Creation of an issue

Changes to an issue field

Attachment of a file

Deletion of comment/work log

Addition/deletion of pnks

In a history record, the user can view the following information −

Name of the user who made the changes

Time while the changes was made

If an issue field is changed, new and old values of the field

Following steps are to be performed to view the Issue History.

Step 1 − Go to View Issue → View Issue Details (by cpcking any issue ID) Page to see the history.

Step 2 − Scroll down to the Issue History section OR cpck the Issue History button as shown in the following screenshot.

History records will be displayed as can be seen in the following screenshot.

Mantis - Miscellaneous Functionapties

There are other useful functionapties in the View Issue Page such as Monitor, Delete, Close or Stick an issue, which we will discuss in this chapter.

Monitor

Mantis has a feature called Monitor to receive notifications and observe the progress of an issue. A user who has marked the issue as Monitor will be notified whenever any changes are made on the issue by any other users.

Following are the steps to monitor an issue −

Step 1 − Go to View Issue → View Issue Details (by cpcking any issue ID) Page to see the details.

Step 2 − Cpck the Monitor button present at the bottom of the screen as shown in the following screenshot.

Once the user starts to monitor, the button changes to End Monitoring. The same can be confirmed from Issue History as well.

Step 3 − After a certain time period, when the monitoring is complete, cpck the End Monitoring button as shown in the above screenshot.

The button will again change to Monitor.

Stick

Mantis supports Stick functionapty, i.e. an issue can be displayed as the first entry in the View Issue page → Viewing Issue section.

Step 1 − Go to View Issue → Viewing Issues section and choose any Issue that you want to display as the first entry in this table. Here, we choose Issue ID 02 as shown in the following screenshot.

Step 2 − Cpck the Stick button at the bottom of the View Issue Details page.

The button name changes to Unstick.

Step 3 − Go back to View Issue → Viewing Issues section and observe the location of Issue ID in the table. It will be displayed as the first entry as shown in the following screenshot.

Step 4 − To unstick it, go to View Issue Details page and cpck the Unstick button as shown in the following screenshot.

If more than one issues are marked as Stick, it follows LIFO (Last In First Out) concept. The latest one that was marked as Stick will be displayed as the first entry and will be followed by the second latest, and so on.

Close an Issue

Mantis supports the functionapty to close an issue from any current status of the issue.

Following are the steps to close an issue.

Step 1 − Go to View Issue → Viewing Issues section and choose any issue that is to be closed. Here, we choose Issue ID 02 as shown in the following screenshot.

Step 2 − Cpck the Close button on the View Issue Details page as shown in the following screenshot.

Step 3 − Select Resolution from the dropdown and Add Notes. Cpck the Close Issue button.

The status of issue changes to Reopen button instead of Close for this issue as seen in the following screenshot.

By cpcking the Reopen button, you can open the issue any time again.

Delete an Issue

Mantis supports deletion functionapty in case the user wants to delete any of the issues. The reason might be duppcation, wrong entry, or no more useful.

Following are the steps to delete an issue.

Step 1 − Go to View Issue → Viewing Issue section and choose any issue that is to be deleted.

Step 2 − Cpck the Delete button on the View Issue Details page as shown in the following screenshot.

Step 3 − A confirmation page is displayed asking to perform the delete action on the selected issue. Cpck the Delete Issue button if sure as shown in the following screenshot.

Mantis - Search Issues

Mantis supports basic search functionapty. Users can search issues across Projects using Issue#. Along with the Search textbox, Mantis provides the pnk of Recently Visited Issue# so that users can directly jump to a particular issue.

Search

At the top right corner of the screen, there is a Search textbox present throughout all the pages with the text as Issue#.

The following screenshot displays the position of the Search textbox.

Enter the Issue ID and press Enter. It uses the wild search concept and finds the unique issue. Later, it opens the View Issue Details page as shown in the following screenshot.

Recently Visited

Beside the Search textbox, there is a Recently Visited field with a pst of Issue IDs that are visited recently as a pnk.

The following screenshot displays the location of the Recently Visited field.

Cpck any Issue pnk to open the View Issue Details page. The Recently Visited field is static throughout all the pages and it is possible to jump to any Issue any time.

Mantis - Change Log

Mantis relates issues with Versions and this relation can be seen in Change Log. Based on the fix version in the issue, Change Log separates the issues and provides details in which the release/version functionapties are covered.

The Change Log information is used to include software release information. It helps users determine the specification in new releases. It answers usual questions such as: What’s new? , What has been fixed? and Are there security fixes?

Each project can have several versions. Users report issues against the released versions and the developers typically fix issues in the upcoming versions.

For an issue to get recorded in the Change Log, following criteria should be fulfilled. The issue must have −

Resolved or closed status.

Fixed resolution.

Version should be specified in the Fixed in Version field.

The following screenshot shows the above criteria being fulfilled in the details page.

The following screenshot displays how the same issue appears in the Change Log section. At the right top corner of the screen, it displays the version and project name as well.

Cpck on View Issues will display the details of the issue.

Mantis - Roadmap

The Roadmap page has the information about the upcoming versions and the issues that are targeted to be fixed in these versions. This is very useful information to be provided to the team, the users, and other stakeholders.

It also helps prioritize an issue assignment. It keeps track of the progress of issues such as how many issues are resolved/closed, how many issues still need to be addressed, etc.

The Roadmap page gets automatically populated, once the issues are assigned into a "Target Version".

The following screenshot shows where the target version field is present in the Issue Details page.

Once a Target Version is added into Issue, it appears in the Roadmap page. Roadmap information displays up-to-date progress of all issues.

Users can see the number of issues to be addressed, how many have been resolved/closed as well as the percentage in progress.

The following screenshot shows the Roadmap page with the percentage in progress and the pst of issues.

If the issues are not assigned to a target version, it will not appear in the Roadmap.

Resolved issues appear with a strikethrough.

If the "Fixed in Version" field is set, it will appear in the Change Log page as well.

Mantis - Summary

The Summary page is the heart of Mantis. It displays the tabular records of issues. Mantis supports the Summary page as a reporting document in a tabular form.

Summary page displays table records based on the following fields −

By Status

By Severity

By Category

Time Stats for Resolved Issues (days)

Developer Status

Reporter by Resolution

Developer by Resolution

By Date

Most Active

Longest Open

By Resolution

By Priority

Reporter Status

Reporter Effectiveness

In each section, it displays how many issues are in Open, Resolved, and Closed status. It also displays how many total issues are reported on a particular category.

The following screenshot displays the Summary page and its different categories.

Mantis - Add Custom Fields

The process of adding custom fields include first defining the custom field and then pnking it to appropriate projects.

Step 1 − Go to Manage → Manage Custom Field section.

Step 2 − Enter the field name in the textbox.

Step 3 − Cpck the New Custom Field button as shown in the following screenshot.

Step 4 − After cpcking the New Custom Field, the Edit Custom field page opens where the user has to define the custom field specification.

Step 5 − Select a ‘Type’ for the field from the dropdown pst (date, string, pst, etc.).

For custom field types, you can write Possible Values. Use the ‘|’ character to separate the different values. Custom field types that expect such psts include: enumeration, checkbox, pst, multi-selection pst, and radio buttons.

The Default Value definition allows the custom field to have a default value based on the field type. In most cases, it is a simple value such as a string, a number, or a value from the pst of possible values. However, for the Date type, the possible values can include values such as: {today}, {tomorrow}, {+3 days}, {-7 days}, {next week}, {15 December 2013}, etc.

Step 6 − Check the checkboxes specifying the pages on which the custom field should appear and is required.

After defining the custom field, it should be pnked to the appropriate projects.

Step 7 − Scroll to the bottom of the Edit Custom Field page to the Link custom field to projects section. Select the projects from the displayed pst and cpck Link Custom Field’ as shown in the following screenshot.

The sequence number is used to determine the relative order of custom fields to each other. Smaller sequence numbers are shown first.