This is an old revision of the document!
Mantis Frequently Asked Questions
How do I customise Severities, Priorities and Statuses?
Does Mantis 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 Mantis issues written in .NET, and many others.
Does Mantis provide an XML-RPC interface?
Not, but it provides a SOAP webservice interface. See above.
Does Mantis integrate with XOOPS?
Does Mantis integrate with Geeklog?
Does Mantis integrate with Postnuke?
Does Mantis integrate with PHProject?
Does Mantis integration with CVS?
Does Mantis integration with Subversion?
How do I get help?
Use Mantis Forums
or mantisbt-help at lists dot sourceforge dot net
for posting questions. Our preference goes to the forums.
Use mantisbt-dev at lists dot sourceforge dot net for development related discussions.
Use Mantis Manual
comments to identify a problem with the documentation or to contribute hints that are ought to be part of the documentation.
Use mantisbt-lang at lists dot sourceforge dot net for discussions relating to localisation to a specific language.
How do I contribute patches?
If you are about to implement a major feature, it is strongly recommended to get in touch with the developers. Such interaction will make it much more likely that your mods be applied to Mantis distribution.
A patch should be attached as a single zip or .tar.gz file.
A patch should include a copy of all new files / modified files as well as a diff (patch) file (if possible).
A patch should only contain one feature. If a patch has a mixed bag of features, it makes it harder to understand and apply.
If you require feedback from developers relating to the patch, then post a message to mantisbt-dev at lists dot sourceforge dot net which refers to the issue including your patch. Ideally, the feedback will be added to the issue as notes. If not, then the patch owner should summarise the feedback as notes.
Fixes and updates to the patch should be attached to the same issue as should be marked clearly. With every attachment there should be a note that refers to the file name and specifies the updates done.
Join Mantis IRC
channel for realtime discussions with developers.
Patches should following Mantis coding style.
Keep your patches up-to-date as new Mantis versions are released.
How do I become a Mantis developer?
How do I contribute localisation to a new language?
Migration to Mantis
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 Mantis. Use this Mantis patch which adds support for importing CSV files into the Mantis database.
Migration from Bugzilla to Mantis
Migration from GNATs to Mantis
See this issue for a Perl script that migrates GNATs data to Mantis.
Migration from Task Vision to Mantis
See this issue for a C# console application that migrates TaskVision to Mantis.