• agileMantis - Scrum for MantisBT
• MantisStats Plugin: a collection of free statistical reports for your MantisBT
• CustomReporter Plugin
• Customer Management Plugin
• EmailReporting Plugin
• EventLog
• InlineColumnConfiguration Plugin
• FilterPageEdit Plugin
• GanttChart Plugin
• iCalExport
• LinkedCustomFields Plugin
• MachineAD
• ManTweet
• RelatedIssuesExport Plugin
• RecurrCall
• Reminder Plugin
• MantisBT S/MIME Plugin
• SourceIntegration
• Tasks
• The Poser
• Automatic linking to MediaWiki and ViewVC from Mantis
• IssueViewers
• RemoteMantisImport

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.

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

A plugin is simply a directory with files in it. To install one:

1. Download and unzip the plugin files to your computer
2. Upload the plugin directory and the files it contains files under <yourMantisRoot>/plugins
3. In MantisBT go to page Manage > Manage Plugins. You will see a list of installed and currently not installed plugins
4. Click the Install link to install a 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.

• Make your request by sending an e-mail to The MantisBT development mailing list (you will need to signup if you are not already subscribing to the list), indicating
  • 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. $this→name and $this→description)
  • the list of people who should have push access to the new repository (i.e. their Github user IDs), including yourself

• If the plugin is a GitHub public repository that you own
  1. We will
     • Create a Team for you to manage the plugin
     • Setup access rights
     • Notify you by e-mail when it's done
  2. You can now transfer ownership of the repository, following the instructions on GitHub Help
  3. Let us know when you're done

• If the plugin is not yet on GitHub (e.g. hosted elsewhere or a local repo)
  1. We will
     • Create a blank repository
     • Setup access rights
     • Notify you by e-mail when it's done
  2. Clone the new repository
  3. Commit and Push your changes

• Don't forget to Reference your plugin in the list above.
  If you would like to have your own wiki page, again send us an e-mail and we'll create it for you

This section describes how to manage the teams in the organization; it is targeted at the organization's owners.

1. Create the new repo
2. Create the new team
3. Name it after the plugin being added, i.e. Plugin XXXX
4. Grant permissions
   • 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
5. Add members
6. Add the repository
7. Grant the core-developers team access to the repository

follow the steps above, skipping 1, 6 and 7. Then, once the original owner has completed the transfer,

• Revoke Administrative access from the Plugin XXXX group
• Perform step 7