MantisBT安装与管理指南

需积分: 9 130 浏览量更新于2024-07-25 收藏 769KB PDF 举报

"Mantis Bug Tracker Administration Guide_2013" MantisBT 是一款基于Web的bug跟踪系统，自2000年11月首次公开发布以来，它已逐渐成熟并获得了广泛的欢迎，成为最受欢迎的开源bug/问题追踪系统之一。这个系统由PHP编写，支持包括MySQL、MS SQL、PostgreSQL和DB2在内的多种数据库后端。 MantisBT作为一个PHP脚本，可以在任何支持PHP并兼容其支持的一种DBMS的操作系统上运行。已知MantisBT在Windows、Linux、OS/2、Mac OS X、System i以及各种Unix操作系统上运行良好。此手册主要针对负责评估、安装和维护公司内部MantisBT的人，通常我们将这个人称为MantisBT管理员。本指南的目的是为MantisBT管理员提供参考，涵盖了从系统评估到安装、配置和日常维护的所有关键步骤。手册包含了关于MantisBT的详细信息，如其功能、系统需求、安装过程、数据库配置、用户管理、权限设置、问题报告和处理流程等。 MantisBT的功能包括但不限于：问题报告、问题分类与优先级设定、状态跟踪、版本控制、邮件通知、用户权限管理、自定义字段以及与其他软件的集成。此外，手册还可能涉及系统的升级、备份恢复策略、性能优化以及故障排查等内容。在安装过程中，管理员需要确保服务器环境满足PHP和所选数据库系统的最低要求，并进行必要的安全配置。手册将指导管理员如何配置Web服务器（如Apache或Nginx）以支持MantisBT，以及如何设置数据库连接参数。对于维护部分，管理员需了解如何添加和管理用户，设置不同用户的角色和权限，以确保项目团队成员可以有效协作。同时，监控系统性能，定期备份数据库，以及保持MantisBT更新以获取最新的功能和安全修复也是管理员的重要职责。此外，手册可能还会介绍MantisBT的定制化选项，如自定义报告、插件和主题，使系统更好地适应团队的工作流程和需求。MantisBT的社区和开发者提供了丰富的资源，包括插件、教程和讨论论坛，帮助用户解决遇到的问题。 "Mantis Bug Tracker Administration Guide_2013" 是一本全面的指南，旨在帮助管理员成功部署和管理MantisBT，以实现高效、可靠的bug追踪和问题管理。

Chapter 2. Installation

5. http://www.7-zip.org/

6. http://www.mantisbt.org/bugs/view.php?id=12735

7. http://www.phpmyadmin.net/

8. http://www.wincron.com/

9. http://dev.mysql.com/doc/refman/5.1/en/mysqlhotcopy.html

10. http://sourceforge.net/projects/automysqlbackup/

Chapter 3. User Management

Creating User Accounts

In MantisBT, there is no limit on the number of user accounts that can be created. Typically,

installations with thousands of users tend to have a limited number of users that have

access level above REPORTER.

By default users with ADMINISTRATOR access level have access to create new user

accounts. The steps to do that are:

• Click "Manage" on Main Menu.

• Click "Manage Users" (if not selected by default).

• Click "Create New Account" button just below the alphabet key.

• Enter user name, email address, global access level (more details about access levels

later). Other ﬁelds are optional.

• Click "Create Users".

Creating a user triggers the following actions:

• Creating a user in the database.

• If email notiﬁcations ($g_enable_email_notiﬁcation) is set to ON, then the user will re-

ceive an email allowing them to activate their account and set their password. Other-

wise, the account will be created with a blank password.

• If email notiﬁcations ($g_enable_email_notiﬁcation) is set to ON, users with access level

about $g_notify_new_user_created_threshold_min will get a notiﬁcation that a user ac-

count has been created. Information about the user like user name and email address are

provided. The IP of the user that created the account is also included.

When the ’Protected’ ﬂag is set on a user account, it indicates that the account is a shared

account (e.g. demo account) and hence users logged using such account will not be allowed

to change account preferences and proﬁle information.

The anonymous user account speciﬁed with the $g_anonymous_account option will al-

ways be treated as a protected user account. When you are creating the anonymous user

account, the ’Protected’ ﬂag is essentially ignored because the anonymous user is always

treated as a protected user.

Enabling/Disabling User Accounts

The recommended way of retiring user accounts is to disable them. Scenarios where this

is useful is when a person leaves the team and it is necessary to retire their account.

Once an account is disabled the following will be enforced:

• All currently active sessions for the account will be invalidated (i.e. automatically logged

out).

• It will no longer be possible login using this account.

• No further email notiﬁcations will be sent to the account once it is disabled.

• The user account will not show anymore in lists like "assign to", "send reminder to", etc.

Chapter 3. User Management

The disabling process is totally reversible. Hence, the account can be re-enabled and all

the account history will remain intact. For example, the user will still have issues reported

by them, assigned to them, monitored by them, etc.

Deleting User Accounts

Another way to retire user accounts is by deleting them. This approach is only recom-

mended for accounts that have not been active (i.e. haven’t reported issues). Once the

account is deleted, any issues or actions associated with such account, will be associated

with user123 (where 123 is the code of the account that was deleted). Note that associated

issues or actions are not deleted.

As far as the underlying database, after the deletion of a user, records with the user id

as a foreign key will have a value that no longer exists in the users table. Hence, any tools

that operate directly on the database must take this into consideration.

By default administrators are the only users who can delete user accounts. They can

delete accounts by clicking Manage, Manage Users, locating the user to be deleted and

opening it details page, then clicking on the "Delete User" button which deletes the user.

Note that "Deleting Users" is not a reversible process. Hence, if it is required to re-add the

user account, it is not possible to recreate the user account so that it gets the same ID and

hence retains its history. However, manually creating a record in the users table with the

same id, can possibly do that. However, this approach is not recommended or supported.

User Signup

For open source and freeware projects, it is very common to setup MantisBT so that users

can signup for an account and get a REPORTER access by default (conﬁgurable by the

$g_default_new_account_access_level conﬁguration option). The signup process can be

enabled / disabled using the $g_allow_signup conﬁguration option, which is enabled by

default.

If user signup is enabled, then it is required that $g_send_reset_password is ON as well,

and the e-mail settings properly conﬁgured (see Email Conﬁguration).

If email notiﬁcations ($g_enable_email_notiﬁcation) is set to ON, users with access level

about $g_notify_new_user_created_threshold_min will get a notiﬁcation that a user ac-

count has been created. Information about the user like user name, email address, IP ad-

dress are included in the email notiﬁcation.

Forgot Password and Reset Password

It is pretty common for users to forget their password. MantisBT provides two ways to

handle such scenario: "Forgot Password" and "Reset Password".

"Forgot Password" is a self service scenario where users go to the login page, ﬁgure out

they don’t remember their password, and then click the "Lost your password?" link. Users

are then asked for their user name and email address. If correct, then they are sent an email

with a link which allows them to login to MantisBT and change their password.

"Reset Password" scenario is where a user reports to the administrator that they are not

able to login into MantisBT anymore. This can be due to forgetting their password and

possibly user name or email address that they used when signing up. The administrator

then goes to Manage, Manage Users, locates the user account and opens its details. Under

the user account details, there is a "Reset Password" button which the administrator can

click to reset the password and trigger an email to the user to allow them to get into Man-

tisBT and set their password. In the case where email notiﬁcations are disabled, resetting

password will set the password to an empty string.

Chapter 3. User Management

Changing Password

Users are able to change their own passwords (unless their account is "protected"). This

can be done by clicking on "My Account", and then typing the new password in the "Pass-

word" and "Conﬁrm Password" ﬁelds, then clicking "Update User". Changing the pass-

word automatically invalidates all logged in sessions and hence the user will be required

to re-login. Invalidating existing sessions is very useful in the case where a user going onto

a computer, logs into MantisBT and leaves the computer without logging out. By changing

the password from another computer, the session on the original computer automatically

becomes invalidated.

Pruning User Accounts

The pruning function allows deleting of user accounts for accounts that have been created

more than a week ago, and they never logged in. This is particularly useful for users who

signed up with an invalid email or with a typo in their email address address.

The account pruning can be done by administrators by going to "Manage", "Manage

Users", and clicking the "Prune Accounts" button inside the "Never Logged In" box.

Authorization and Access Levels

MantisBT uses access levels to deﬁne what a user can do. Each user account has a

global or default access level that is associated with it. This access level is used as the

access level for such users for all actions associated with public projects as well as

actions that are not related to a speciﬁc project. Users with global access level less than

$g_private_project_threshold will not have access to private projects by default.

The default access levels shipped with MantisBT out of the box are VIEWER,

REPORTER, UPDATER, DEVELOPER, MANAGER and ADMINISTRATOR. Each

features has several conﬁguration options associated with it and identiﬁes the required

access level to do certain actions. For example, viewing an issue, reporting an issue,

updating an issue, adding a note, etc.

For example, in the case of reporting issues, the required access level is conﬁgurable us-

ing the $g_report_bug_threshold conﬁguration option (which is defaulted to REPORTER).

So for a user to be able to report an issue against a public project, the user must have a

project-speciﬁc or a global access level that is greater than or equal to REPORTER. How-

ever, in the case of reporting an issue against a private project, the user must have project

speciﬁc access level (that is explicitly granted against the project) that is higher than RE-

PORTER or have a global access level that is higher than both $g_private_project_threshold

and $g_report_bug_threshold.

Note that project speciﬁc access levels override the global access levels. For example, a

user may have REPORTER as the global access level, but have a MANAGER access level

to a speciﬁc project. Or a user may have MANAGER as the global access level by VIEWER

access to a speciﬁc project. Access levels can be overridden for both public and private

projects. However, overriding access level is not allowed for users with global access AD-

MINISTRATOR.

Each feature typically has multiple access control conﬁguration options to deﬁnes what

access level can do certain operations. For example, adding a note may require REPORTER

access level, updating a note my require DEVELOPER access level, unless the own was

owned by the same user and in this case REPORTER access level. Such threshold conﬁg-

uration options can be set to a single access level, which means users with such threshold

and above are authorized to do such action. The other option is to specify an array of ac-

cess level which indicates that users with the explicitly speciﬁc thresholds are allowed to

do such actions.

It is also worth mentioning that the access levels are deﬁned by the

$g_access_levels_enum_string conﬁguration option, and it is possible to customize such

剩余94页未读，继续阅读

spartan_117

粉丝: 3
资源: 1

MantisBT安装与管理指南

轻量级的开源缺陷跟踪系统——MANTISBT(Mantis Bug Tracker)

Mantis Bug Tracker

Mantis Bug Tracker v1.2.8 多国语言版

Mantis Bug Tracker (MantisBT)多国语言版1.2.8

基于PHP的缺陷跟踪系统 Mantis Bug Tracker 多国语言版.zip

PHP实例开发源码-php 缺陷跟踪系统 Mantis Bug Tracker 多国语言版.zip

信息安全_数据安全_Roaming_Mantis：An_Anatomy_Of_A_D.pdf

XPE_disk2.rar_MANTIS~1.CAB_XPE_XPE_disk2

mantis-manual.rar_文章/文档_Unix_Linux_

Mantis Bug Tracker 1.2.3 安装配置教程

最新资源