MantisBT

MantisBT
Name	MantisBT
Developer	MantisBT Team
Released	2000
Programming language	PHP
Operating system	Cross-platform
License	GNU General Public License

MantisBT is an open-source issue tracking and project management system designed for reporting, tracking, and resolving software defects and tasks. It provides workflow customization, role-based access control, and integration points for source control, continuous integration, and notification systems. Originating from a community-driven project, it has been adopted by academic institutions, corporations, and open-source foundations for coordinating development, release management, and support activities.

History

MantisBT originated in 2000 amid the rise of open-source projects such as Linux, Apache HTTP Server, MySQL, PHP, and Drupal, reflecting a need similar to tools like Bugzilla, Trac (software), and Redmine for lightweight issue tracking. Early contributors drew inspiration from projects and institutions including SourceForge, Freshmeat, Debian Project, and companies like Mozilla and Canonical (company), which influenced feature priorities for scalability, localization, and workflow. Over subsequent releases, governance and code contributions came from individuals and organizations akin to Google, IBM, Microsoft, and academic groups associated with MIT and Stanford University, enabling integrations with version control systems such as Git, Subversion, and CVS (software). Community-driven milestones and roadmap discussions have been shaped by events and foundations like FOSDEM, Linux Foundation, Open Source Initiative, and Apache Software Foundation conferences.

Features

MantisBT offers issue reporting, customizable fields, and workflow states comparable to functionality found in JIRA (software), GitLab, Phabricator, and YouTrack (JetBrains). Notification and email templates support protocols and services including SMTP, IMAP, and third-party providers used by organizations like Amazon (company) and Google LLC. Time tracking, roadmap planning, and changelog generation enable release practices followed by projects such as Ubuntu, Fedora Project, and KDE. Plugins and extensions provide integration with continuous integration tools like Jenkins, Travis CI, and CircleCI, and with communication platforms such as Slack, Mattermost, and IRC. Internationalization features parallel efforts seen in Mozilla Firefox, LibreOffice, and OpenOffice.org for translating strings and managing locale teams.

Architecture and Technology

The core is implemented in PHP and relies on relational databases such as MySQL, MariaDB, PostgreSQL, and SQLite, following patterns similar to WordPress and MediaWiki. The web frontend uses HTML, CSS, and JavaScript, integrating with libraries and frameworks used by projects like jQuery, Bootstrap (front-end framework), and Font Awesome. Authentication and single sign-on options mirror approaches utilized by LDAP, Active Directory, and identity providers such as Okta and Auth0. Integration adapters facilitate webhook and API interactions akin to those provided by GitHub, Bitbucket, and GitLab (software). The plugin architecture and event hooks resemble extensibility models used in Drupal, Jenkins, and Eclipse ecosystems.

Deployment and Installation

Typical deployments follow LAMP or LEMP stacks employed by platforms like Ubuntu, Debian, CentOS, Fedora Project, and Red Hat Enterprise Linux. Installation procedures reference package management practices seen in apt (software), yum, and dnf and containerization patterns popularized by Docker (software), Kubernetes, and OpenShift. Backup and migration strategies align with database administration practices from PostgreSQL Global Development Group recommendations and tooling used by Percona and phpMyAdmin. Hosting choices mirror those of projects hosted on GitHub, GitLab.com, Bitbucket, and cloud providers like Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Security and Permissions

Access control supports role-based permissions and project-level roles similar to models in JIRA (software), GitLab, and Redmine. Security practices for hardening installations draw on guidance from organizations such as OWASP, CERT Coordination Center, and standards like ISO/IEC 27001. Authentication options include integrations with LDAP, SAML, and OAuth 2.0 providers commonly used by enterprises such as Facebook and Microsoft. Vulnerability tracking and patch management reflect coordination strategies seen in CVE, NIST, and incident response processes practiced by teams at Cisco and Cloudflare.

Community and Development

Development is coordinated by volunteer contributors, corporate sponsors, and maintainers similar to governance models of Apache Software Foundation, Debian Project, and Linux Kernel Mailing List. Communication channels include mailing lists, forums, and issue trackers paralleling those used by GNU Project, Free Software Foundation, and projects hosted on GitHub. Contribution workflows mirror pull request and review practices popularized by GitHub, GitLab, and Gerrit and involve CI pipelines like those in Jenkins and Travis CI to validate changes. Translation, documentation, and advocacy efforts take cues from communities around Mozilla Developer Network, Wikimedia Foundation, and Stack Overflow.

Notable Use Cases and Integrations

Organizations in academia, government, and industry have implemented the software for bug tracking and project management, in contexts similar to deployments by NASA, European Space Agency, National Institutes of Health, Sony, and Intel Corporation. Integrations with version control and CI/CD systems reflect practices used by Linux Kernel, Chromium, GNOME Project, Kubernetes, and OpenStack contributors. Ticketing workflows and service desk linkages follow patterns seen in integrations between ServiceNow, Zendesk, Atlassian Confluence, and Freshdesk, enabling cross-team coordination in enterprises like Airbus and Siemens.

Category:Issue tracking systems