Mantis 简明教程

Mantis - Quick Guide

Mantis - Introduction

Mantis Bug Tracker 是一款开源网页应用程序工具。用于缺陷生命周期过程中 bug 跟踪。Mantis 除了支持 bug 跟踪外，还支持发布功能来管理项目或软件各个版本。

Mantis Bug Tracker is an open source web-based application 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 还被称为 “MantisBT”，代表 “Mantis Bug Tracker”。Mantis 的名称和标识指的是螳螂科昆虫。在软件中，它被称为 bug。

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 提供演示版、下载版（用于设置自己的 Mantis）和托管版工具。它支持多项问题跟踪和生命周期功能，以及版本管理。

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

Mantis 的开发始于 2000 年，由伊藤谦三郎发起。2002 年，其他团队成员（Jeroen Latour、Victor Boctor 和 Julian Fitzell）相继加入。Mantis 的基本版本 1.0.0 于 2006 年 2 月发布。

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

2012 年，GitHub 成为 Mantis 项目源代码的官方存储库。

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 lifecycle.
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

Sr.No.	Specification & Description
1	Application Copyright The copyright is taken by MANTIS System Limited Company (“MANTIS SYSTEM”) License is taken under GNU General Public License Version 2
2	Tool Scope It can be used as a Bug Tracking System
3	Stable Release 2.1.0 Onwards. Latest release is 2.5.1
4	Developed Language PHP as a coding language and SQL for database Tool supports 49 languages
5	Operating System Cross Platforms ( Platform Independent software)
6	System Requirements Web Server - Mantis is mainly tested with Microsoft IIS and Apache PHP - Mandatory extensions are mysqli, pgsql, oci8, sqlsrv, mbstring Database - MySQL, PostgreSQL
7	Client Requirements Firefox 45 and above IE 10 and above Chrome/Safari/Opera
8	User Interface Available API Desktop GUI Mobile UI

Mantis - Features

Mantis 支持一系列广泛的功能，以吸引 QA 和其他利益相关者跟踪问题。以下是 Mantis 的核心功能。

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.

Mantis - Installation

Mantis 是一个网络应用程序，为个人或属于同一公司/项目的请求用户组提供私人网站。

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

Mantis 可以在服务器端运行。它是一个基于 PHP 的应用程序，并支持所有操作系统平台，如不同版本的 Windows、Linux、Mac 等。它也以移动视图支持移动浏览器。

Mantis can be run at the server side. It is a PHP-based application 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

由于 Mantis 是一个网络应用程序，因此它遵循客户端/服务器的概念。这意味着 Mantis 可以集中安装在服务器上，用户可以使用任何计算机上的网站通过网络浏览器与之交互。

Since Mantis is a web-application, it follows the concept of client/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 mysqli, 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.
Client Requirements − Firefox 45 and above, IE 10 and above, Chrome, Safari, and Opera.

用户可以分别手动或自动安装所有需求以使用 Mantis。

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

Installation of System Requirements

如果用户对安装过程有足够了解，可在安装 Mantis 之前分别逐一安装所有需求。

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

或者，还可以采用多种多合一软件包，它们涵盖所有需求，而且可以通过 exe 文件自动安装到系统中。本文将采用 XAMPP 来轻松安装先决条件。

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 - 转至 https://www.apachefriends.org/index.html 并点击 Windows 用的 XAMPP，如下图所示。

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

Step 2 − 将显示一个弹出窗口，提示保存该文件。单击“保存文件”。将开始下载该文件。

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

Step 3 − 运行 .exe 文件以运行安装向导。单击 .exe 文件后，将显示 XAMPP 设置向导。单击“下一步”。

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

以下屏幕截图显示了 XAMPP 设置向导。

The following screenshot shows the XAMPP setup wizard.

Step 4 − 下一个向导将显示所有组件文件，如以下屏幕截图所示。选择组件后单击“下一步”。

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

Step 5 - 提供 XAMPP 将要安装到的文件夹名称，然后点击下一步。

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

随即显示“准备安装”向导。

Ready to Install wizard is displayed.

Step 6 − 单击“下一步”开始安装。

Step 6 − Click Next to start the installation.

Step 7 − 成功安装后，将询问是否要启动控制面板。选中该复选框，然后单击“完成”。随即会打开 XAMPP 控制面板，如以下屏幕截图所示。

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

Step 8 − 单击 Apache 和 MySQL 的“启动”按钮，如上述屏幕截图所示，这两个组件是 Mantis 所必需的。

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

Step 9 − 若要验证是否已经正确安装 Apache、PHP 和 MySQL 等所有先决条件，请导航至任意浏览器，键入 http://localhost 并按 Enter 键。它将显示 XAMPP 的信息中心。单击右上角的 phpAdmin，如以下屏幕截图所示。

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. Click phpAdmin at the right top corner as shown in the following screenshot.

下一个屏幕截图将显示“常规设置”、“应用程序设置”以及数据库、Web 服务器和 phpMyAdmin 的详细信息。

The next screenshot will display General Settings, Application 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 − 要下载 Mantis，请转到 https://www.mantisbt.org/ and click 下载。

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

Step 2 − 在下一个页面上单击“下载”，如下面的屏幕截图所示。

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

Step 3 − 再次单击“下载”，如下面的屏幕截图所示，然后保存 .zip 文件。

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

Step 4 − 转到它已安装的 XAMPP 文件夹，然后导航到 htdocs 文件夹。解压缩下载的 mantis 并将其放置在如下面的屏幕截图所示。

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 − 将文件夹名称 mantis 2.5.1 重命名为 mantis 以获得更好的网址。

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

Step 6 − 现在打开一个浏览器，在导航栏中输入 http://localhost/mantis 并按 Enter。它将显示 mantis 的索引，如下面的屏幕截图所示。单击 mantis-2.5.1。

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. Click mantis-2.5.1.

它将显示预安装页面，如下面的屏幕截图所示。

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

Step 7 − 转到“安装”部分并进行更改（如果需要）。然后，单击“安装/升级数据库”按钮。

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

安装完成后，它将显示检查安装页面，并标记为良好，即 Mantis 已正确安装。

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 − 要启动 mantis，请使用 URL http://localhost/mantis and click mantis-2.5.1 。它将显示 Mantis 的登录页面，如下面的屏幕截图所示。

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

Note − 确保 Web 服务器和数据库在使用 URL 之前都正在运行，否则将显示“问题加载页面”错误。

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 − 将用户名提供为“管理员”并单击“登录”。它将要求输入密码。使用“root”作为密码，然后单击“登录”。

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

成功登录后，它将显示 Mantis 仪表板。

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

Mantis - Trial Setup

Mantis 是一个开源工具。但是，Mantis 支持演示和托管版本，用户可以在下载工具之前亲身体验。

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 − 转到 https://www.mantisbt.org/ 并单击“演示”，如以下屏幕截图所示。

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

Step 2 − 在下一页上，单击“开始免费试用”。

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

Step 3 − 填写注册页面中的所有详细信息，然后单击“注册我”按钮，如下面的屏幕截图所示。

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

设置试用版 URL 和 30 天免费试用需要 1-2 分钟。设置成功后，用户将能够看到 Mantis 的仪表板/我的视图页面。

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.

以下屏幕截图显示了 Mantis 的“我的视图”页面。

The following screenshot shows the My View page of Mantis.

Mantis - Login

Step 1 − 要登录 Mantis，请转到示例演示网站。它将打开一个登录页面。

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

Step 2 − 填写您注册的电子邮件地址/用户名，然后单击“登录”。

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

Step 3 − 成功验证用户名后，它将询问密码。输入密码并单击“登录”按钮。

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

以下屏幕截图显示了如何使用凭据登录 Mantis。

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.

单击“忘记密码？”。

Click Lost your password?

提供用户名和电子邮件地址以获取密码重置链接。单击“提交”，如下图所示。

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

用户将收到一封电子邮件，其中包含用于重置密码的 URL。

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.

以下屏幕截图显示了成功登录后 Mantis 的仪表盘/我的视图页面。

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/individual basis.

存在于 Mantis 页面顶部的导航栏在 Mantis 的所有页面/屏幕中都是相同的。报告问题、邀请用户、管理员和帮助是导航栏的主要链接。

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 links of the navigation bar.

菜单栏上存在几个部分（从左上角到左下角）。这些部分是 Mantis 的核心，涵盖所有主要功能。菜单栏有以下部分 - 我的视图、查看问题、报告问题、更改日志、路线图、摘要和管理。

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 functionalities. 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.

用户可以单击问题 ID 和名称导航到特定问题。

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

在页面的右侧，用户可以看到入门指南。在这里，新用户可以了解使用 Mantis 的基本功能。提供了时长几分钟的教程，介绍如何维护项目结构的用户。

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

以下屏幕截图显示 Mantis 的我的视图页面概览。

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

在入门部分下方，还有另一个部分名称为时间线。

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

在这里，用户可以看到在一周或给定时间线内执行哪些活动，例如谁创建了问题、创建了多少个问题、谁最近选择了哪个问题等。

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

以下屏幕截图显示我的视图页面的时间线部分。

The following screenshot displays the Timeline 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 - 以管理员身份登录。

Step 1 − Login as Administrator.

Step 2 - 转到位于左侧菜单栏中的“管理”部分。

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

Step 3 - 单击“管理项目”选项卡。

Step 3 − Click “Manage Projects” tab.

Step 4 - 要创建新项目，请单击新建项目按钮。要编辑现有项目，请单击项目名称。在这里，“我的项目”是现有的默认项目。

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

以下屏幕截图显示如何创建新项目。

The following screenshot shows how to create a new project.

Step 5 - 单击新建项目/项目名称后，新建项目表单打开。

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

Step 6 - 在创建之前输入以下字段 -

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 public projects. Private projects are only visible to users assigned to the project or to administrators.

Step 7 − 现在，单击“添加项目”按钮。

Step 7 − Now, click 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

要选择项目，导航功能位于页面右上角。要查看此选项，用户应有权至少查看 2 个项目。用户有权查看的项目列在“所有项目”选项中。

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 listed under the “All Projects” option.

如果用户从列表中选择“所有项目”选项，它将显示用户有权查看的所有已列出的项目。

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

要查看单个项目，用户应从列表中选择特定项目。

To view an individual project, the user should select the particular project from the list.

以下截屏显示如何选择项目。

The following screenshot displays how to select Projects.

Archive a Project

如果用户希望从可用项目列表中隐藏某个项目，则从顶部下拉列表中，存档该项目就是解决方案。

If the user wants to hide a project from the list of projects as available, from the top dropdown list, 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 − 转到管理 → 管理项目。

Step 1 − Go to Manage → Manage Projects.

Step 2 − 单击需要存档/取消存档的项目名称。

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

Step 3 − 勾选/取消勾选启用字段，进行取消存档/存档。

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

Step 4 − 单击“更新项目”。

Step 4 − Click 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 dividing 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.

用户可以创建特定于项目的类别，或在所有项目中全局定义该类别。Mantis 支持一个名为“常规”的预定义全局类别。当在项目之间移动缺陷时，此类别用作默认类别，并且目标项目中没有源类别。

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 − 转到管理 → 管理项目选项卡。

Step 1 − Go to Manage → Manage Projects tab.

Step 2 − 在文本框中输入类别名称，然后单击“添加类别”。

Step 2 − Enter the Category name in the text box and click 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 clicking 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 - 要配置类别，请转到“管理”→“管理项目”→“全局类别”

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

Step 2 - 点击“编辑”配置特定类别，如下一个屏幕截图所示。

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

Step 3 - 在“编辑项目类别”中，从下拉列表中选择“分配给”。

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

Step 4 - 点击“更新类别”。

Step 4 − Click 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 - 要删除一个类别，请转到“管理”→“管理项目”。

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

Step 2 - 点击要删除的特定类别。然后，从“操作”列中点击“删除”按钮，如下一个屏幕截图所示。

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

Step 3 - 在点击“删除”后，Mantis 会显示一条警告消息并要求确认，用户是否要删除特定类别。点击“删除类别”按钮，如下一个屏幕截图所示。

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

如果问题列在已删除的类别下，在删除后，这些问题将自动更新并显示为无类别。

If the issues are listed 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.

将项目更新和开发组织为多个发布或版本。版本可以被命名为 1.0、1.1 或根据功能的发布日期命名为“20171020”。

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.

在问题表单中，有 3 个与版本相关的字段 - 产品版本、目标版本和修复版本。

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

Product Version 中记录了用户发现在哪个版本中发现了此问题并记录此问题的详细信息。

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

Target Version 是一个未来或当前版本，在该版本中显示预定修复此问题的时间。此信息会自动填充到项目路线图中。

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 中显示了此问题在哪个版本中得到实际修复或实现。此信息会自动填充到项目更改日志中。

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 − 要添加或更新项目的版本，请转到管理 → 管理项目选项卡。

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

Step 2 − 单击必须添加版本的项目名称。

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

Step 3 − 向下滚动到版本部分。

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 − 要更新版本，请单击上文显示的编辑按钮。

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

Step 5 − 用户可以根据需要更新所有字段。单击更新版本，如以下屏幕截图中所示。

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

Mantis - Issue Lifecycle

生命周期表示问题的不同阶段或状态。生命周期从报告问题开始，当问题得到解决或关闭时结束。问题主要可以有 3 个阶段 − 打开、解决和关闭。但是，Mantis 支持更多状态，稍后将对此进行解释。

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 − 这是用户报告新问题时的第一个状态。下一状态可能是“反馈”、“已确认”、“已确认”、“已分配”或“已解决”。

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 − 此状态用于审查目的。在分配给团队成员之前，将进行审查流程，以确定问题的有效性和问题团队。下一状态可能是“新建”、“已分配”或“已解决”。

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 − 发展团队使用此状态发送有关收到问题或同意报告人的问题的确认。但是，他们可能尚未重现此问题。下一个状态是“已分配”或“已确认”。

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 − 发展团队通常使用此状态来反映他们已确认和重现此问题。下一个状态是“已分配”。

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 − 此状态用于反映此问题已分配给团队成员之一，并且团队成员负责修复此问题并积极地处理此问题。下一状态是“已解决”。

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 − 此状态用于反映此问题已得到修复或解决。此问题可以在以下任何解决办法中解决。例如，可以将问题称为已为“已修复”、“重复”、“无法修复”、“无需更改”或其他原因而解决。下一个状态是“关闭”，或者如果问题正在重新打开，则会将问题标记为“反馈”。

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 − 此状态反映出该问题已关闭并已成功验证。不需要对该问题采取进一步操作。问题关闭后，问题将从查看问题页面中隐藏。

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.

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 - 如果用户有权访问多个项目，首先选择屏幕右上角的项目，问题将在其中报告。

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 - 单击项目筛选器旁边顶部显示的报告问题链接，或单击左侧菜单栏中的报告问题部分。

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 - 单击报告问题后，它将打开带有必填字段和可选字段的输入问题详细信息页面。

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

Step 4 - 正确输入所有详细信息。以下为字段：

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 - 如果用户希望报告一个以上问题，选中报告停留复选框，该复选框将在提交问题后返回到问题报告页面。

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 - 现在，单击页面底部的提交问题按钮。

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 - 成功创建后，用户导航到查看问题页面，在那里可以看到新报告的问题。

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

Mantis - Import Issues

用户可以使用 CSV 文件一次创建多个问题。CSV 文件是逗号分隔文件。

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

Rules for CSV File

在创建 CSV 文件时，必须考虑以下几点 −

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 Delimited).
The user should switch to the project before starting the CSV import steps.
All entries should be made in a Notebook application. 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 lines “\n” 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 like the following −

wires

General

Assigned to

administrator

1.0

error

wires

General

error message on wrong credential

new

1.0

on successful

wires

General

welcome page on successful login

Assigned to

administrator

1.0

Import CSV

要导入 CSV 文件，用户应当执行以下步骤 −

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

Step 1 − 转至管理 → 管理插件。

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

Step 2 − 检查 CSV 导入器插件是否已安装。

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

Step 3 − 如果未安装，请单击安装，如下面的屏幕截图所示。

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

Step 4 − 由于已安装插件中没有 CSV 导入器，转至可用插件部分，找到 CSV 导入器。单击安装，如下面的屏幕截图所示。

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

Step 5 − 安装后，用户可以在已安装插件部分看到 CSV 导入器。导入 CSV 文件部分也存在。单击导入 CSV 文件，如下面的屏幕截图所示。

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

Step 6 − 单击导入 CSV 文件后，将打开从 CSV 文件导入问题。根据文件和要求选择各种选项，如下面的屏幕截图所示。之后，单击选择文件浏览文件，然后单击上传文件。

Step 6 − After clicking 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, click Choose File to browse the file and then click Upload file.

Step 7 − 成功上传后，用户可以看到按列排列的数据。在其下方，用户需要将这些列映射到 Issue 表单的不同字段，如下图所示。

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 − 映射后，单击“导入文件”按钮。

Step 8 − After mapping, click 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 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 - 从左侧菜单中单击“查看问题”。

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 - 要设置筛选器，请单击“字段名称”。例如：本例中的报告人员。它将显示可用于选择的可用下拉列表。

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 - 在选择其他筛选器后，单击“应用筛选器”以按以下屏幕截图所示搜索结果。

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 - 在单击“应用筛选器”按钮后，问题将显示在屏幕底部的“查看问题”部分中，如下面的屏幕截图所示。

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 - 通过单击“保存当前筛选器”，用户可以保存筛选器并在需要时使用。

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

Step 6 - 在单击“保存当前筛选器”按钮后，将打开以下表单以输入“筛选器名称”。输入名称并选中“公开”、“适用于所有项目”。单击“保存当前筛选器”。

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 - “保存筛选器”按钮旁边会显示一个下拉列表，用户可以在其中查看当前保存的筛选器名称并从中选择筛选器。该下拉列表显示所有可用的筛选器列表，如下面的屏幕截图所示。

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 - 从菜单中转到“查看问题”，设置筛选器，然后单击“应用筛选器”。

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

Step 2 - 现在，转到“查看问题”部分并确保显示问题。

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

Step 3 - 选择要打印的问题，然后单击“打印报告”，如下面的屏幕截图所示。

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

问题显示为浏览器页面，并在屏幕左上角带有 Word 和 HTML（Internet Explorer）标志，如下面的屏幕截图所示。

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 - 单击 Word 符号，它将下载包含错误详细信息的 word 文件。示例 word 文件将如下所示：文件名称将为<项目名称>.doc，其中包含每个问题的完整详细信息。

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 - 单击 HTML 符号，一个新的浏览器将打开，其中包含每个问题的完整详细信息，如下面的屏幕截图所示。

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

要导出为 CSV/Excel 文件，需要执行以下步骤：

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

Step 1 - 从菜单中转到“查看问题”，设置筛选器并单击“应用筛选器”。

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

Step 2 - 转到页面底部的“查看问题”部分并确保问题得到显示。

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

Step 3 - 选择需要导出的问题，然后单击 CSV/Excel 导出，如下图所示。

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.

示例 CSV 文件如下所示。

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

示例 Excel 文件如下所示。

The sample Excel file will look like 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 - 通过单击问题 ID 在“查看”页面中打开问题。

Step 1 − Open the issue in View page by clicking 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 - 打开“查看问题详情”页面后，单击“编辑”按钮，如下图所示。

Step 2 − After opening the View Issue Details page, click 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 - 编辑信息后，单击“更新信息”按钮，如下图所示。

Step 3 − After editing the information, click 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 duplicate issue within the same project. Cloned issues can be treated as a new issue and edited like 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 link 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 links
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 − 通过单击问题 ID 在“查看”页面中打开问题。

Step 1 − Open an issue in the View page by clicking 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 − 打开“查看问题详情”页面后，单击“克隆”按钮，如下图所示。

Step 2 − After opening the View Issue Details page, click 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 − 在页面的底部，为“与父级问题的关联”字段编写原始问题 ID。选择原始问题和克隆问题的关联，如下图所示。

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 − 部分“从父级问题复制扩展数据”中有 2 个复选框 − 复制问题备注和复制附件。如果您想复制相同内容，请勾选这些复选框。默认情况下，不会选中它们。

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 − 选择后，单击“提交问题”按钮。

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

成功提交后，将生成新的问题 ID 并打开查看问题页面。

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

Mantis - Advanced Features

在报告问题的同时，除了某些常规信息外，Mantis 还支持一些高级功能，使其更具信息性和实用性。在本章中，我们将讨论这些高级功能。

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 支持 @mentions 以引起用户注意并发送有关问题或备注的通知，即使他们不在通知列表中。

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

这是吸引某人注意力的简单方法。只需在问题备注或说明中引用同事，就可以通过链接向问题详细信息发送备注详细信息。

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 link 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 超链接到用户页面，并在格式化备注/问题时突出显示。

@mentions is hyperlinked to the user page and highlighted when notes/issues are formatted.

在这种情况下，用户会收到常规电子邮件通知以及 @mentions 通知。但是，@mentions 通知格式简单且主题不同。

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

以下屏幕截图显示了收到的 @mentions 电子邮件。

The following screenshot displays the received email for @mention.

Send Reminder

发送提醒是 @mentions 的替代功能。此功能用于引起特定用户的注意。例如，产品负责人向团队发送提醒，以更新评论。

Send Reminder is the alternate functionality 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 通常建议使用 @mentions。但是，它是一项可选功能。

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

转到“查看问题”并单击“问题 ID”以打开“查看”页面。

Go to the View Issue and click 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 clicking the Send a reminder button, a message box appears. On the left side, there is a list of users and on the right side messages can be typed. After selecting the user and writing the message, click 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

截至目前，Mantis 支持以下 HTML 标签，它们可以用来给说明和笔记字段中的标签加格式 - p、li、ul、ol、br、pre、I、b、u、em、strong。然而，Mantis 并不建议给文本加格式。

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

文本电子邮件将使用原始标签而不是格式化文本。Mantis 有一项计划朝着 Markdown 加格式的方向发展，它将弃用 HTML 标签。

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.

除了 Markdown 支持之外，Mantis 正计划支持 html 电子邮件。这些特性将共同解决现有解决方案的局限性。然而，截至目前，对于 Markdown 或 HTML 电子邮件支持，还没有具体的时间表。

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

Attach Files

Mantis 支持向问题附加多个文件。当报告问题时，用户可以通过点击选择文件按钮来附加文件。也可以通过点击上传文件按钮从查看问题中附加文件。另外一种方法，是在编辑问题模式下附加文件。

Mantis supports attaching multiple files to an issue. A user can attach the file while reporting the issue by clicking the Choose File button. The file can also be attached from the View Issue by clicking 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.

点击上面标记的按钮并浏览要上传的文件。上传成功后，文件将会显示在该按钮的下方。

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

然后，点击添加笔记。文件将被添加到活动部分，如下一个截图所示。

Then, click 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 支持以下状态 - 新的、反馈、已确认、确认、关闭和已解决。用户可以根据完成的工作更改问题的状态。

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 - 转到查看问题部分并点击将被更改为该状态状态的问题 ID。

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

Step 2 - 点击“状态更改为”旁边的下拉菜单并选择一个状态。

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

Step 3 - 在选择后，点击如以下截图所示在查看问题详情部分显示的“状态更改为”按钮。

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 - 在那之后，点击<状态> 问题按钮。举例来说：对于反馈，问题请求反馈页面将打开。

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 − 点击请求反馈按钮并且问题状态将变成反馈，如下面的截图所示。

Step 5 − Click 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 duplicates or are related to each other, upstream downstream dependency as parent/child issue.

Create a Link to Another Issue

问题可以在任何时间点关联在一起，在使用查看问题或编辑问题页面报告问题时关联。

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

Step 1 − 点击查看问题页面。

Step 1 − Click the view issue page.

Step 2 − 导航到关联部分。

Step 2 − Navigate to Relationships section.

Step 3 − 选择问题与链接问题的关系。例如：打开的问题是另一个问题的父/重复问题。

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

Step 4 − 现在，输入问题 ID 并点击添加按钮，如下面的截图所示。

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

添加之后，您可以在关联部分看到链接的问题。这是超链接，因此也可以导航到链接的问题。

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

您使用问题 ID 之间的“|”字符可以一次为多个问题添加关联。

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

下面的截图显示了链接的问题。

The following screenshot displays the linked issue.

Delete a Link

Step 1 − 转到包含指向该问题的链接的查看问题详细信息页面。

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

Step 2 − 向下滚动并转到关联部分。

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

Step 3 − 点击删除图标，如下面的截图所示。

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

Step 4 − 将显示确认弹出窗口，如下面的截图所示。点击删除按钮。

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

Mantis - Move an Issue

Mantis 具有将问题从一个项目移动到另一个项目的功能。

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

One Issue At a Time

Step 1 − 转到需要移动到另一个项目的查看问题详细信息页面。

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

Step 2 − 点击移动，如下面的截图所示。

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

Step 3 − 在移动项目页面，选择问题将移动到的新项目，并点击移动项目按钮，如下面的截图所示。

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

Multiple Issues at a Time

Step 1 − 转到查看问题页面。

Step 1 − Go to the View Issue page.

Step 2 − 设置筛选器并导航至“查看问题”部分，您将在此找到问题列表。

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

Step 3 − 选中所有需要移动的问题的复选框。

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

Step 4 − 从屏幕底部的下拉菜单中选择“移动”选项，然后单击“确定”。

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

以下屏幕截图显示如何一次移动多个问题。

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

Step 5 − 在“将问题移动至”页面中，选择问题将移动到的新项目，并单击“移动问题”按钮，如下图所示。

Step 5 − In the Move Issues to page, select the new project, where the issue will move and click 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 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 − 转至“查看问题”→“查看问题详细信息”（通过单击任何问题 ID）页面以查看历史记录。

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

Step 2 − 向下滚动至“问题历史记录”部分，或单击“问题历史记录”按钮，如下图所示。

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.

Mantis - Miscellaneous Functionalities

“查看问题”页面中还有其他有用的功能，例如，监视、删除、关闭或固定问题，我们将在本章中讨论这些功能。

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 有一个名为监视的功能，用于接收通知并观察问题的进展。已将问题标记为监视的用户在其他任何用户对问题进行任何更改时都会收到通知。

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 − 转至“查看问题”→“查看问题详细信息”（通过单击任何问题 ID）页面以查看详细信息。

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

Step 2 − 单击屏幕底部出现的“监视”按钮，如下图所示。

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 - 在特定时间段后，当监控完成时，单击“结束监控”按钮，如上图所示。

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 支持粘贴功能，即问题可在“查看问题”页面 → “查看问题”部分中显示为第一个条目。

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 - 转到“查看问题”→“查看问题”部分并选择您想要显示在此表中的第一个条目的任何问题。此处，我们选择问题 ID 02，如下面的屏幕截图所示。

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 - 单击“查看问题详细信息”页面底部的“粘贴”按钮。

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

按钮名称会变更为“取消粘贴”。

The button name changes to Unstick.

Step 3 - 返回到“查看问题”→“查看问题”部分并观察表中问题 ID 的位置。它将显示为第一个条目，如下面的屏幕截图所示。

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 - 若要取消粘贴，请转到“查看问题详细信息”页面并单击取消粘贴按钮，如下面的屏幕截图所示。

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

如果将多个问题标记为“粘贴”，则会遵循 LIFO（后进先出）概念。最新标记为“粘贴”的问题将显示为第一个条目，然后依次显示最近第二个，依此类推。

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 支持从问题的任何当前状态关闭问题的功能。

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 - 转到“查看问题”→“查看问题”部分并选择要关闭的任何问题。此处，我们选择问题 ID 02，如下面的屏幕截图所示。

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 - 单击“查看问题详细信息”页面上的“关闭”按钮，如下面的屏幕截图所示。

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

Step 3 - 从下拉列表中选择“解决”并“添加备注”。单击“关闭问题”按钮。

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 支持删除功能。原因可能是重复、输入错误或不再有用。

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 - 转到“查看问题”→“查看问题”部分并选择要删除的任何问题。

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

Step 2 - 如以下屏幕截图所示，在查看问题详情页面上单击删除按钮。

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

Step 3 - 确认页面显示，询问是否在选定的问题上执行删除操作。如果确认，请单击删除问题按钮，如以下屏幕截图所示。

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.

Mantis - Search Issues

Mantis 支持基本搜索功能。用户可以使用问题 # 在项目中搜索问题。除了搜索文本框外，Mantis 还提供最近访问的问题 # 的链接，以便用户可以直接跳转到特定问题。

Mantis supports basic search functionality. Users can search issues across Projects using Issue#. Along with the Search textbox, Mantis provides the link 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.

输入问题 ID 并按 Enter。它使用通配搜索概念并找到唯一问题。稍后，它打开查看问题详情页面，如以下屏幕截图所示。

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

在搜索文本框旁边，有一个最近访问字段，其中列出了最近访问的问题 ID 作为链接。

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

以下屏幕截图显示了最近访问字段的位置。

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

单击任何问题链接以打开查看问题详情页面。最近访问字段在所有页面中都是静态的，并且可以随时跳转到任何问题。

Click any Issue link 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 将问题与版本相关联，这种关联可以在变更日志中看到。基于问题中的修复版本，变更日志将问题分开，并提供涵盖发布/版本功能的详细信息。

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 functionalities 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.

点击查看问题将显示问题的详细信息。

Click 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 list 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

概要页面是 Mantis 的核心。它显示问题的表格记录。Mantis 支持以表格格式将概要页面作为报告文档。

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 linking it to appropriate projects.

Step 1 − 转到“管理 → 管理自定义字段”部分。

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

Step 2 − 在文本框中输入字段名称。

Step 2 − Enter the field name in the textbox.

Step 3 − 单击“新建自定义字段”按钮，如下图所示。

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

Step 4 − 单击“新建自定义字段”后，将打开“编辑自定义字段”页面，用户必须在其中定义自定义字段规范。

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

Step 5 − 从下拉列表（日期、字符串、列表等）中为字段选择一个“类型”。

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

对于自定义字段类型，您可以编写可能的值。使用 ‘|’ 字符分隔不同的值。期望此类列表的自定义字段类型包括：枚举、复选框、列表、多选列表和单选按钮。

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

“默认值”定义允许自定义字段根据字段类型具有默认值。在大多数情况下，它是一个简单值，例如字符串、数字或可能值的列表中的值。然而，对于“日期”类型，可能的值可以包括以下值：{today}、{tomorrow}、{+3 days}、{-7 days}、{next week}、{15 December 2013} 等。

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 list 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 − 选中指定自定义字段应显示并必需的页面的复选框。

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 linked to the appropriate projects.

Step 7 − 滚动到“编辑自定义字段”页面的底部，找到“将自定义字段链接到项目”部分。从显示的列表中选择项目，然后单击“链接自定义字段”，如下图所示。

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 list and click '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.