WP Mantis

WP Mantis Install Statistics

0
100%
Today: 0 Yesterday: 0 All-time: 2,739 downloads
WP Mantis Icon

Try plugin: WP Mantis

We'll create fresh WordPress site with WP Mantis installed. You have 20 minutes to test the plugin after that site we'll be deleted.

Takes ~10 seconds to install.

About WP Mantis

Extended Version of "WP Mantis Table". Allows to view Changelogs, Roadmaps and Buglists from MantisBT in Wordpress Pages and Post.

0


0


0


0


0

updated: 13 years ago
since: 14 years ago
author: Niklas Rother

Description

Eine Deutsche Version kann hier gefunden werden

Original Work by Robert Torres. His Version was not working, since he had a typo in a variable. I fixed this error and
extendet this Plugin with some new Features like Changelogs, Roadmaps etc.

This plugin for WordPress 2.8 and above allows you to insert information from a Mantis Bug Tracker
into a wordpress page or post. The plugin is perfect for projects which use WordPress for blogging,
but also utilize Mantis for their bug tracking/issue tracking. You can include bug lists,
changelogs and roadmaps.

After you installed the Plugin you have to do the following steps:

  1. Create a user in Mantis wich represents your blog. You could name him ‘wordpress’. This user needs at least Reporter
    Rights due a limitation in Mantis, but you can see the botton of the page to find out, how to change this.
  2. Configure the Plugin.
  3. Add [Mantis] to the post or page where you want to appear the infomation from Mantis. See below for further instructions.

About the Shortcode

You must provide options in the Shortcode:

  • To include a bug list use [Mantis bugs proj_id=x]. Replace x with the ID of the project wich you want to display.
    You can find the ID in the URL of the Mantis Management Page for this project.
  • To include a roadmap use [Mantis roadmap ver_id=x]. Replace x with the ID of the Version for that you want to display
    the roadmap. You can find this ID in the URL, when you view a single Roadmap in Mantis.
  • To include a changelog use [Mantis changelog ver_id=x]. See the instruction above this to find the ID.

When including a roadmap or a changelog you can speficify a project and version name instead of the ID:
[Mantis roadmap proj_name=my_project ver_name=1.2.3] or you can use a project ID and a version name: [Mantis roadmap proj_id=x ver_name=y]
The ver_name Paramter is optional, if missing the full changelog/roadmap for the project will be displayed

If you use the ‘bugs’ option, you can add the ‘exclude_stat’ or ‘include_stat’ parameter. After the eqal sign you can add (comma seperated)
the IDs of the statuses to exclude or include. (You can not use include and exclude at the same time, of course!)
So if you dont want to include closed and fixed bugs you would write [Mantis bugs proj_id=1 exclude_stat=90,80]
Here is a list of the IDs:

  • 10 New
  • 20 Feedback
  • 30 Acknowledged
  • 40 Confirmed
  • 50 Assigned
  • 80 Resolved
  • 90 Closed

With the limit paramter you can limit the displayed bugs. To display the latest 5 fixed bugs you would write
[Mantis bugs proj_id=1 include_stat=80 limit=5]

You can change the table background color for each status and use the localized status names from your mantis installation.

Why the Mantis User needs Reporter rights

This plugin uses the Mantis SOAP API to get the bug information. And to access this API the user needs at least Reporter
right. To change this you can create a ‘mc_config_inc.php’ file in your ‘/api/soap’ directory with the following
content:

Now Viewer rights are suffiant for the user.

Further plans: (eventually)

  • Only include the CSS/JavaScript if the [Mantis] shortcode is in the content

Translations

The original plugin is in english, but you can translate in your langguage, since the pot file is included. If I should include
your translation, email me: info at niklas-rother dot de. So far the following translations are included:

  • German/Deutsch
  • Frensch/Francais

Know Bugs

  • The changelog and roadmap is in the default language, not in the language of the user. At this point I dont see a change to fix this.