Table of Contents

Frequently Asked Questions


How do I customise Severities, Priorities and Statuses?

See Customising Enumerations in the MantisBT manual.


Does MantisBT provide a webservice interface?

See the MantisConnect project which provides a PHP webservice that can be used from any language that supports SOAP webservices. MantisConnect also includes client libraries for .NET, Java and Cocoa.

MantisConnect also includes sample applications that uses the provided client libraries to provide useful tools. This includes an Eclipse plug-in written in Java, a NAnt task to submit MantisBT issues written in .NET, and many others.

MantisConnect now comes as part of the standard MantisBT installation package and can be found under the '{$mantis_install_dir}/api/soap' directory. To see what functionality is currently provided via MantisConnect, check the WSDL available here.

Does MantisBT provide an XML-RPC interface?

No, but it provides a SOAP webservice interface. See above reference to MantisConnect project.

Is there a MantisBT version for Smart Phones / PDAs?

Yes, checkout MantisWAP. MantisWAP provides a very light weight interface for MantisBT access through a smart phone or PDA. It is optimize for speed and minimization of consumed bandwidth.

Does MantisBT integrate with Drupal?

Checkout BugBits.

Does MantisBT integrate with XOOPS?

We are aware of two XOOPS Ports:

Does MantisBT integrate with Geeklog?

MantisBT 0.18.3 port for Geeklog

Does MantisBT integrate with Postnuke?

MantisBT 0.18.0a4 port for Postnuke

Does MantisBT integrate with PHProject?

MantisBT port for PHProject

Does MantisBT integrate with Joomla?

MantisBT Single-Sign-On with Joomla - has security issue, not recommended to install at this time.

Joomla plugin - uses MantisBT SOAP API to display and add issues.

Does MantisBT integrate with CVS?

Yes. See the following resources:

Does MantisBT integrate with Subversion?

Yes. See the following resources:

Does MantisBT integrate with Source Control tools?

Scmbug is a system that integrates software configuration management (SCM) with bug-tracking. It aims to be a universal tool that will glue any source code version control system (such as CVS, Subversion, and Arch) with any bug-tracking system (such as Bugzilla, MantisBT, and Request Tracker).


How do I get help?


How do I contribute patches?

More details on the procedure in the Getting your Patches into Mantis page

How do I become a MantisBT developer?

How do I contribute localisation to a new language?

Migration to MantisBT

The information below might be out of date; the scripts may have been written to export from an old version of the source tracker, and target an equally obsolete version of MantisBT.

Use with caution and at your own risks.

Migration from Custom Bugtrackers

A lot of companies use a custom bug tracker that is built in-house. Obviously there won't be a standard script that can be used to import that. Hence, the way to approach this would be to export the data to a csv file then import it into MantisBT. Use this MantisBT patch which adds support for importing CSV files into the MantisBT database.

Migration from Bugzilla to MantisBT

See also the notes in issue #8071

Migration from GNATs to MantisBT

See this issue for a Perl script that migrates GNATs data to MantisBT.

Migration from Task Vision to MantisBT

See this issue for a C# console application that migrates TaskVision to MantisBT.

Migration from FlySpray to MantisBT

See this issue for a Perl script that migrates FlySpray to MantisBT.