This is an old revision of the document!
Note that the above list is by no means exhaustive.
If you authored one or more plugins which are not referenced here, feel free to update this list and create the corresponding wiki page.
Where to find the plugins
MantisBT plugins can be found at https://github.com/mantisbt-plugins.
There is an older plugin repository at http://git.mantisforge.org. (some of the plugins there were moved to github.com/mantisbt-plugins, so first check github.com)
Please note that MantisForge repository is currently offline
More plugins can be found at http://www.mantisbt.org/bugs. Typically they are stored as issue attachments using own projects or project “mantisbt” and category “Plugins”.
How to install a plugin
A plugin is simply a directory with files in it. To install one:
Download and unzip the plugin files to your computer
Upload the plugin directory and the files it contains files under <yourMantisRoot>/plugins
In MantisBT go to page Manage > Manage Plugins. You will see a list of installed and currently not installed plugins
Click the Install link to install a plugin.
The GitHub mantisbt-plugins organization
Hosting a new plugin
If you have authored a new Plugin and would like to have it hosted in our GitHub mantisbt-plugins organization,
here is the simple process to follow:
If you don't have a GitHub account yet, sign up
, it's free.
a link to the repository (we usually review the code before including it in the Organization)
the plugin's name and a short description (if not provided, we'll use the information in the source code, i.e.
the list of people who should have push access to the new repository (i.e. their Github user IDs), including yourself
This section describes how to manage the teams in the organization;
it is targeted at the organization's owners.
| Team name || Description
| Owners || Organization's administrators
| Core developers || MantisBT core team members, have Push access to all plugins (this is maintained manually)
| Plugin XXXX || One team per plugin, granting Push access to the plugin
When adding a new plugin
Name it after the plugin being added, i.e. Plugin XXXX
When transferring an existing GitHub repo, select Push, Pull and Administrative
Note: Admin rights are required to transfer ownership, so they will be granted temporarily and removed afterwards
When creating a new plugin (blank repo), select Push & Pull
Add the repository
When transferring ownership of an existing repository
follow the steps above, skipping 1, 6 and 7.
Then, once the original owner has completed the transfer,