Frequently Asked Questions

This section of the Wiki is not well maintained. Expect to get broken links and outdated information!

See Customising Enumerations in the MantisBT manual.

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.

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

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.

Checkout BugBits.

We are aware of two XOOPS Ports:

• MantisBT 1.0.3 port for XOOP by nobu
• MantisBT 0.18.3 port for XOOP by gstarrett

MantisBT 0.18.3 port for Geeklog

MantisBT 0.18.0a4 port for Postnuke

MantisBT port for PHProject

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.

Yes for old versions, no for versions >= 1.3.0

Yes. See the following resources:

• Sample post commit file
• Manual page for source control integration
• ScmBug Project

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

• Use MantisBT 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 Bug Tracker for reporting feature requests and bugs.
• Use MantisBT 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.

• 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 MantisBT distribution.
• Patches should be attached to a Mantis Bug Tracker issue.
• 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 MantisBT IRC channel for realtime discussions with developers.
• Patches should following MantisBT coding style.
• Keep your patches up-to-date as new MantisBT versions are released.

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

• Contribute patches that follow the above guidelines.
• Join the developers on the IRC channel.
• Participate/Contribute to MantisBT Forums.
• Participate/Contribute to mailing lists.

• Use strings_english.txt as the basis for the new localisation file.
• Consider using UTF8 encoding.
• Submit an issue into the Mantis Bug Tracker and attach a compressed version of the file.

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.

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.

• PHP script implemented by afontquerni.
• Another PHP script
• Perl script originally written by Cris Daniluk, with some fixes & improvements by various contributors

See also the notes in issue 8071.

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

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

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