Category: mantis

Mantis – Summary ”; Previous Next 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. Print Page Previous Next Advertisements ”;

Mantis – Miscellaneous Functionalities ”; Previous Next There are other useful functionalities 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 clicking any issue ID) Page to see the details. Step 2 − Click 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, click the End Monitoring button as shown in the above screenshot. The button will again change to Monitor. Stick Mantis supports Stick functionality, 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 − Click 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 click 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 functionality 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 − Click 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. Click 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 clicking the Reopen button, you can open the issue any time again. Delete an Issue Mantis supports deletion functionality in case the user wants to delete any of the issues. The reason might be duplication, 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 − Click 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. Click the Delete Issue button if sure as shown in the following screenshot. Print Page Previous Next Advertisements ”;

Mantis – View Issues ”; Previous Next 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 functionalities of Issues can be accessed through View Issues. We will discuss all of these functionalities 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 − Click 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, click Field name. For example: Reporter in this case. It will display the available dropdown list to select. Step 3 − After the selection of other filters as well, click Apply Filter to search the result as shown in the following screenshot. Step 4 − After clicking 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 clicking the Save Current Filter, the user can save the filter and use whenever required. Step 6 − After clicking the Save Current Filter button, the following form opens to enter Filter Name. Enter the name and check Make Public, Apply for all projects. Click 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 list displays all available filter list 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 click 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 click 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 clicking the Word symbol, it downloads the word file having the details of the bug. The sample word file will look like: The name of the file would be <project name>.doc and it contains complete details of each issue. Step 5 − Click 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 click 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 click 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 like as shown in the following screenshot. The sample Excel file will look like as shown in the following screenshot. Print Page Previous Next Advertisements ”;

Mantis – Features ”; Previous Next 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 Sr.No. Core Feature & Description 1 Collaboration and Hassle Free It makes collaboration with team members and client easy, fast, and professional. As many users can use the same domain and same set of data. It is available only for Licensed product. 2 Email Notification All users or set of team members can get email notification whenever there are any changes, updates, or resolutions on an issue. Email will be triggered for any action taken by any one among a group of users. Voting and watching features to keep an eye on the progress for stakeholders. Use @mention to get the attention of a specific team member for Comments/Description. 3 Access Control Admin can grant access to the users based on individual role. It can be applicable differently for each project. Thus, one person can have different level of access for two different projects. 4 Customization Mantis supports customization at each level. Users can customize fields for issue creation/view. Users can customize fields for issue workflow and notification as well. 5 Dashboard Dashboard displays assigned to me, unassigned, reported by me and many other standard filters to look at all the issues belonging to individual users. Timeline feature allow to keep an eye on what is happening across the project. It displays live stream on the latest actions taken by any team member. 6 Release Management Mantis helps to manage different releases. It supports Project Versions to track releases. Users can create future releases and mark issues for respective release as well. Issues and release information can also be summarized in a Roadmap page for better understanding. 7 Time Tracking Mantis supports its own in-built time tracking feature. Users can easily enter the time spent on a particular issue. It can help make a report on the spent hours for each issue as an individual or as a team. 8 Integration/Plug-in Mantis supports more than 100 add-ins to connect with different softwares to make the work easy. Wide range of add-ins make it universal across the globe – TestLodge, TestRail, TestCollab, Testuff, HipChat, Slack, etc. It also supports Eclipse IDE and JetBrains. 9 Common Features Using Slack and HipChat integration, the team can communicate with each other. Mantis provides SSO (single sign on) access to log into MantisHub using GitHub or BitBucket credentials. 10 Customer Support Mantis Helpdesk is a very popular feature. It allows integrating your support with your internal issue tracking. Using Grasshopper integration, users get direct voicemail line. Print Page Previous Next Advertisements ”;

Mantis – Issue History ”; Previous Next 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 links 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 clicking any issue ID) Page to see the history. Step 2 − Scroll down to the Issue History section OR click the Issue History button as shown in the following screenshot. History records will be displayed as can be seen in the following screenshot. Print Page Previous Next Advertisements ”;

Mantis – Issue Lifecycle ”; Previous Next 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 validity 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”, “duplicate”, “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 validated. No further actions are required on it. Once the issue gets closed, it hides the issue from the View Issues page. Print Page Previous Next Advertisements ”;

Mantis – Change Status ”; Previous Next 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 click the Issue ID of the status that has to change. Step 2 − Click the dropdown beside “Change Status to” and select one of the statuses. Step 3 − After selection, click 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 click 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 − Click the Request Feedback button and the status of issue is changed to feedback as shown in the following screenshot. Print Page Previous Next Advertisements ”;

Mantis – Versions ”; Previous Next 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 functionalities 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 utilize this functionality. 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 − Click 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 click Add Version. Step 4 − To update a Version, click the Edit button as shown above. Step 5 − The user can update all the fields based on the requirement. Click Update Version as shown in the following screenshot. Print Page Previous Next Advertisements ”;

Mantis – Trial Setup ”; Previous Next 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 click Demo as shown in the following screenshot. Step 2 − On the next page, click Start Your Free Trial. Step 3 − Fill all the details in the sign-up page and click 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. Print Page Previous Next Advertisements ”;

Mantis – Report an Issue ”; Previous Next 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 − Click the Report Issue link present at the top beside the project filter OR click 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 clicking 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, click 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. Print Page Previous Next Advertisements ”;