Just enter your username and password and hit the login button. There is also a Save Login checkbox to have the package remember that you are logged in between browser sessions. You will have to have cookies enabled to login.If the account doesn't exist, the account is disabled, or the password is incorrect then you will remain at the login page. An error message will be displayed.The administrator may allow users to sign up for their own accounts. If so, a link to Signup for your own account will be available.The administrator may also have anonymous login allowed. Anonymous users will be logged in under a common account.You will be allowed to select a project to work in after logging in. You can make a project your default selection from the Select Project screen or from your Account Options.SignupHere you can signup for a new account. You must supply a valid email address and select a unique username. Your randomly generated password will be emailed to your email account. If MantisBT is setup so that the email password is not to be emailed, newly generated accounts will have an empty password.

This is the first page you see upon logging in. It shows you the latest news updates for the bugtracker. This is a simple news module (based off of work by Scott Roberts) and is to keep users abreast of changes in the bugtracker or project. Some news postings are specific to projects and others are global across the entire bugtracker. This is set at the time of posting in the Edit News section.The number of news posts is controlled by a global variable. When the number of posts is more than the limit, a link to show "older news" is displayed at the bottom. Similarly a "newer news" is displayed when you have clicked on "older news".There is an Archives option at the bottom of the page to view all listings.ArchivesA title/date/poster listing of ALL past news articles will be listed here. Clicking on the link will bring up the specified article. This listing will also only display items that are either global or specific to the selected project.

Here we can view the issue listings. The page has a set of viewing filters at the top and the issues are listed below.FiltersThe filters control the behavior of the issues list. The filters are saved between browsing sessions but do not currently save sort order or direction.If the number of issues exceeds the "Show" count in the filter a set of navigation to go to "First", "Last", "Previous", "Next" and specific page numbers are added.The Search field will look for simple keyword matches in the summary, description, steps to reproduce, additional information, issue id, or issue text id fields. It does not search through issue notes. Issue List - The issues are listed in a table and the attributes are listed in the following order: priority, id, number of issue notes, category, severity, status, last updated, and summary. Each (except for number of issue notes) can be clicked on to sort by that column. Clicking again will reverse the direction of the sort. The default is to sort by last modification time, where the last modified issue appears at the top. The issue id is a link that leads to a more detailed report about the issue. You can also add issue notes here. The number in the issue note count column will be bold if an issue note has been added in the specified time frame. The addition of an issue note will make the issue note link of the issue appear in the unvisited state. The text in the "Severity" column will be bold if the severity is major, crash, or block and the issue not resolved. The text in the "Updated" column will be bold if the issue has changed in the last "Changed(hrs)" field which is specified in the viewing filters. Each table row is color coded according to the issue status. The colors can be customised through MantisBT Configuration Severities block - prevents further work/progress from being made crash - crashes the application or blocking, major - major issue, minor - minor issue, tweak - needs tweaking, text - error in the text, trivial - being nit picky, feature - requesting new feature - Status new - new issue, feedback - issue requires more information from reporter, acknowledged - issue has been looked at but not confirmed or assigned, confirmed - confirmed and reproducible (typically set by an Updater or other Developer), assigned - assigned to a Developer, resolved - issue should be fixed, waiting on confirmation of fix, closed - issue is closed, Moving the mouse over the status text will show the resolution as a title. This is rendered by some browsers as a bubble and in others as a status line text.

Here is the simple listing of the issue report. Most of the fields are self-explanatory. "Assigned To" will contain the developer assigned to handle the issue. Priority is fully functional but currently does nothing of importance. Duplicate ID is used when an issue is a duplicate of another. It links to the duplicate issue which allows users to read up on the original issue report. Below the issue report is a set of buttons that a user can select to work on the issue. Update Issue - brings up a page to edit all aspects of the issue Assign to - in conjunction with the dropdown list next top the button, this is a shortcut to change the assignment of an issue Change Status to - in conjunction with the dropdown list next top the button, this is a shortcut to change the status of an issue. Another page (Change Status) will be presented to allow the user to add notes or change relevant information Monitor / Unmonitor Issue - allows the user to monitor any additions to the issue by email Create Clone - create a copy of the current issue. This presents the user with a new issue reporting form with all of the information in the current issue filled in. Upon submission, a new issue, related to the current issue, will be created. Reopen Issue - Allows the user to re-open a resolved issue Move Issue - allows the user to move the issue to another project Delete Issue - Allows the user to delete the issue permanently. It is recommended against deleting issues unless the entry is frivolous. Instead issues should be set to resolved and an appropriate resolution category chosen. A panel is provided to view and update the sponsorship of an issue.Another panel is provided to view, delete and add relationships for an issue. Issues can have a parent/child relationship, where the user is warned about resolving a parent issue before all of the children are resolved. A peer relationship is also possible.Below this, there may be a form for uploading file attachments. The Administrator needs to configure the bugtracker to handle file uploads. If uploading to disk is selected, each project needs to set its own upload path. Issue notes are shown at the bottom of the issue report. A panel to add issue notes is also shown.

This page is used to change the status of an issue. A user can add an issue note to describe the reason for change.In addition, the following fields may be displayed for update: Resolution and Duplicate ID - for issues being resolved or closed Issue Handler (Assigned to) any Custom Fields that are to be visible on update or resolution Fixed in Version - for issues being resolved Close Immediately - to immediately close a resolved issue

The layout of this page resembles the Simple Issue View page, but here you can update various issue fields. The Reporter, Category, Severity, and Reproducibility fields are editable but shouldn't be unless there is a gross mis-categorization.Also modifiable are the Assigned To, Priority, Projection, ETA, Resolution, and Duplicate ID fields.As per version 0.18.0, the user can also add an issue note as part of an issue update.

This page changes user alterable parameters for the system. These selections are user specific.My AccountThis allows the user to change their password, screen name, and email address. It also reports the user's access levels on the current and other projects.

This sets the following information: Default project whether the pages used for reporting, viewing, and updating are the simple or advanced views the delay in minutes between refreshes of the view all issues page the delay in seconds when redirecting from a confirmation page to the display page the time order in which notes will be sorted whether to filter email messages based on type of message and severity the number of notes to append to notification emails the default language for the system. The additional setting of "auto" will use the browser's default language for the system.

Profiles are shortcuts to define the values for Platform, OS, and version. This page allows you to define and edit personal shortcuts.

A number of pages exist under the "Manage" link. These will only be visible to those who have an appropriate access level.

This page allow an administrator to manage the users in the system.It essentially supplies a list of users defined in the system. The user names are linked to a page where you can change the user's name, access level, and projects to which they are assigned. You can also reset their passwords through this page.At the top, there is also a list of new users (who have created an account in the last week), and accounts where the user has yet to log in.New users are created using the "Create User" link above the list of existing users. Note that the username must be unique in the system. Further, note that the user's real name (as displayed on the screen) cannot match another user's user name.

This page allows the user to manage the projects listed in the system.Each project is listed along with a link to manage that specific project. The specific project pages allow the user to change: the project name the project description its status whether the project is public or private. Private projects are only visible to users who are assigned to it or users who have the access level to automatically have access to private projects (eg: administrators). afile directory used to store attachments for issues and documents associated with the project. This folder is located on the webserver, it can be absolute path or path relative to the main MantisBT folder. Note that this is only used if the files are stored on disk or via FTP. In case of FTP, the cached version that is saved on the webserver, is stored in the specified path. common subprojects. These are other projects who can be considered a sub-project of this one. They can be shared amongst multiple projects. For example, a "documentation" project may be shared amongst several development projects. project categories. These are used to sub-divide the issues stored in the system. project versions. These are used to create ChangeLog reports and can be used to filter issues. They are used for both the Found In and Fixed In versions. Custom Fields linked to this project Users linked to this project. Here is the place where a user's access level may be upgraded or downgraded depending on their particular role in the project.

This page is the base point for managing custom fields. It lists the custom fields defined in the system. There is also a place to enter a new field name to create a new field.The "Edit" links take you to a page where you can define the details of a custom field. These include it's name, type, value, and display information. On the edit page, the following information is defined to control the custom field: name type. Possible values are listed below. Value constraints (Possible values, default value, regular expression, minimum length, maximum length). Access (who can read and write the field based on their access level). Display control (where the field will show up and must be filled in All fields are compared in length to be greater than or equal to the minimum length, and less than or equal to the minimum length, unless these values are 0. If the values are 0, the check is skipped. All fields are also compared against the regular expression. If the value matches the expression, then the value is stored. For example, the expression "/^-?([0-9])*$/" can be used to constrain an integer.The table below describes the field types and the value constraints. Type Field Contents Value Constraints String text string up to 255 characters Numeric an integer Float a floating point number Enumeration one of a list of text strings Enter the list of text strings separated by "|" (pipe character) in the Possible Values field. The Default value should match one of these strings as well. This will be displayed as a dropdown menu. Email an email address string up to 255 characters When displayed, the value will also be encapsulated in a mailto: reference. Checkbox zero or more of a list of text strings Enter the list of text strings separated by "|" (pipe character) in the Possible Values field. The Default value should match one of these strings as well. This will be displayed as a list of text strings with a checkbox beside them. List one of a list of text strings Enter the list of text strings separated by "|" (pipe character) in the Possible Values field. The Default value should match one of these strings as well. This will be displayed as a multi-line dropdown menu. Multiselection List zero or more of a list of text strings Enter the list of text strings separated by "|" (pipe character) in the Possible Values field. The Default value should match one of these strings as well. This will be displayed as a multi-line dropdown menu. Date text string defining a date This is displayed as a set of dropdown menus for day, month, and year. Defaults should be defined in yyyy-mm-dd format. The display entries are used as follows: Entry Meaning Display Only On Advanced Page If checked, the field will NOT be shown on the simple issue displays Display When Reporting Issues If checked, the field will be shown on the report issues displays Display When Updating Issues If checked, the field will NOT be shown on the update issue and change status displays Display When Resolving Issues If checked, the field will NOT be shown on the update issue displays and change status displays, if the new status is resolved. Display When Closing Issues If checked, the field will NOT be shown on the update issue displays and change status displays, if the new status is closed. Required On Report If checked, the field must be filled in on the issue reports. Required On Update If checked, the field must be filled in on the update issue and change status displays. Required On Resolve If checked, the field must be filled in on the update issue and change status displays, if the new status is resolved. Required On Close If checked, the field must be filled in on the update issue and change status displays, if the new status is closed. Notes on Display Be careful not to set both a required attribute and show only on advanced display. It may be possible to trigger a validation error that the user cannot recover from (i.e., field is not filled in).

This page allows the definition of global profiles accessible to all users of the system. It is similar to the user definition of a profile consisting of Platform, OS and Version.

This set of pages control the configuration of the MantisBT system. Note that the configuration items displayed may be on a project by project basis.These pages serve two purposes. First, they will display the settings for the particular aspects of the system. If authorized, they will allow a user to change the parameters. They also have settings for what access level is required to change these settings ON A PROJECT basis. In general, this should be left alone, but administrators may want to delegate some of these settings to managers.

This page covers the adjustment of the settings for many of the workflow related parameters. For most of these, the fields are self explanatory and relate to a similarly named setting in the configuration file. At the right of each row is a selector that allows the administrator to lower the access level required to change the particular parameter.The values changeable on this page are: Title Variable Description Report an Issue $g_report_bug_threshold threshold to report an issue Status to which a new issue is set $g_bug_submit_status status issue is set to when submitted Update an Issue $g_update_bug_threshold threshold to update an issue Allow Issue to be closed on Resolve $g_allow_close_immediately allow close immediately on resolve Allow Reporter to close an issue $g_allow_reporter_close allow reporter to close issues they reported Monitor an issue $g_monitor_bug_threshold threshold to monitor an issue Handle Issue $g_handle_bug_threshold threshold to handle (be assigned) an issue Assign Issue $g_update_bug_assign_threshold threshold to be in the assign to list Move Issue $g_move_bug_threshold threshold to move an issue to another project. This setting is for all projects. Delete Issue $g_delete_bug_threshold threshold to delete an issue Reopen Issue $g_reopen_bug_threshold threshold to reopen an issue Allow reporter to reopen Issue $g_allow_reporter_reopen allow reporter to reopen issues they reported Status to which a reopened Issue is set $g_bug_reopen_status status issue is set to when reopened Resolution to which a reopened Issue is set $g_bug_reopen_resolution resolution issue is set to when reopened Status where an issue is considered resolved $g_bug_resolved_status_threshold status where bug is resolved Status where an issue becomes read-only $g_bug_readonly_status_threshold status where bug is read-only (see update_readonly_bug_threshold) Update readonly issue $g_update_readonly_bug_threshold threshold to update an issue marked as read-only Update Issue Status $g_update_bug_status_threshold threshold to update an issue's status View Private Issues $g_private_bug_threshold threshold to view a private issue Set View Status $g_set_view_status_threshold threshold to set an issue to Private/Public Update View Status $g_change_view_status_threshold threshold needed to update the view status while updating an issue or an issue note Show list of users monitoring issue $g_show_monitor_list_threshold threshold to see who is monitoring an issue Set status on assignment of handler $g_auto_set_status_to_assigned change status when an issue is assigned Status to set auto-assigned issues to $g_bug_assigned_status status issue is set to when assigned Limit reporter's access to their own issues $g_limit_reporters reporters can see only issues they reported. This setting is for all projects. Title Variable Description Add Notes $g_add_bugnote_threshold threshold to add an issue note Update Notes $g_update_bugnote_threshold threshold to edit an issue note Allow users to edit their own bugnotes $g_bugnote_allow_user_edit_delete can a user edit/delete their own issue notes Delete Note $g_delete_bugnote_threshold threshold to delete an issue note View private notes $g_private_bugnote_threshold threshold to view a private issue note View Change Log $g_view_changelog_threshold threshold to view the changelog View Assigned To $g_view_handler_threshold threshold to see who is handling an issue View Issue History $g_view_history_threshold threshold to view the issue history Send Reminders $g_bug_reminder_threshold threshold to send a reminder

This page covers the status workflow. For most of these, the fields are self explanatory and relate to a similarly named setting in the configuration file. At the right of each row is a selector that allows the administrator to lower the access level required to change the particular parameter.The values changeable on this page are: Title Variable Description Status to which a new issue is set $g_bug_submit_status status issue is set to when submitted Status where an issue is considered resolved $g_bug_resolved_status_threshold status where issue is resolved Status to which a reopened Issue is set $g_bug_reopen_status status issue is set to when reopened The matrix that follows has checkmarks where the transitions are allowed from the status on the left edge to the status listed across the top. This corresponds to the $g_enum_workflow array.At the bottom, there is a list of access levels that are required to change the status to the value listed across the top. This can be used, for instance, to restrict those who can close an issue to a specific level, say a manager. This corresponds to the $g_set_status_threshold array and the $g_report_bug_threshold setting.

This page sets the system defaults for sending emails on issue related events. MantisBT uses flags and a threshold system to generate emails on events. For each new event, email is sent to: the reporter the handler (or Assigned to) anyone monitoring the issue anyone who has ever added a issue note the issue anyone assigned to the project whose access level matches a range From this list, those recipients who meet the following criteria are eliminated: the originator of the change, if $g_email_receive_own is OFF the recipient either no longer exists, or is disabled the recipient has turned their email_on_<new status> preference OFF the recipient has no email address entered The matrix on this page selects who will receive messages for each of the events listed down the left hand side. The first four columns correspond to the first four points listed above. The next columns correspond to the access levels defined. Note that because a minimum and maximum threshold are used, a discontinuous selection is not allowed.

The monitor issues feature allows users to subscribe to certain issues and hence get copied on all notification emails that are sent for these issues.Depending on the configuration, sending a reminder to a user about an issue can add this issue to the user's list of monitored issues. Users who reported the issue or are assigned the issue typically don't need to monitor the issue to get the notifications. This is because by default they get notified on changes related to the issue anyway. However, administrators can change the configuration to disable notifications to reporters or handlers in specific scenarios.

Re-open issue button is visible in the issue view pages if the user has the appropriate access level and the issue is resolved/closed. Re-opening a issue will allow users to enter issue notes for the re-opening reason. The issue will automatically be put into the Feedback status.

The delete issues button appears on the issue view pages for the users who have the appropriate access level. This allows you to delete an existing issue. This should only be used on frivolous or test issues. A confirmation screen will prompt you if you really want to delete the issue. Updaters, Developers, Managers, and Administrators can remove issues (you can also configure this).

This is a button that appears on the issue view pages for users that are authorized to close issues. Depending on the configuration, users may be able to close issues without having to resolve them first, or may be able to only close resolved issues. After the button is clicked, the user is redirected to a page where an issue note maybe added.

This button appears in the issue view pages in case of users with access level that is equal to handle_bug_threshold or higher. When this button is clicked the issue is assigned to the user.

This option on the View Issues page allows you to resolve the issue. It will lead you to a page where you can set the resolution state and a duplicate id (if applicable). After choosing that the user can choose to enter an issue note detailing the reason for the closure. The issue is then set to the Resolved state. The reporter should check off on the issue by using the Close Issue button.

MantisBT supports news syndication using RSS v2.0 protocol. MantisBT also supports authenticated news feeds for private projects or installations where anonymous access is not enabled. Authenticated feeds takes a user name and a key token that are used to authenticate the user and generate the feed results in the context of the user's access rights (i.e. the same as what the user would see if they were to logged into MantisBT).To get access to the News RSS as anonymous user, visit the following page: http://www.example.com/mantisbt/news_rss.php While a user is logged in, the RSS links provided in the UI will always provide links to the authenticated feeds, if no user is logged in (i.e. anonymous), then anonymous links will be provided.