Plugin Directory

Test out the new Plugin Directory and let us know what you think.
!This plugin hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

The Bug Genie for WP

Present issues from The Bug Genie in your WordPress blog.

What is the correct TBG address to enter?

As TBG currently enforces you to have /thebuggenie/ in your tracker address no matter what, we add it automatically. So just enter everything before that part. For example, this plugin's bugtracker is located at http://bugs.verrech.net/thebuggenie/tbg4wp so you would enter http://bugs.verrech.net.

What to put as project/issue key?

The project key you chose when creating the project. If you do not administrate TBG yourself, have at look at the URLs it uses. For instance, the project key is the last bit of your project's dashboard URL.

What parameters does `issues` understand?

If only we knew for sure! TBG's API is in a fetal state and not properly documented yet. You can download JSON yourself (append /format/json to a ticket's URL, for example) and try out some combinations. Be warned: it's quite verbose and badly formatted. They are working on it, but this is how it is today. Using the CLI client tbg_cli might be worthwhile, too.

Here is what we have figured out so far:

  • state=(open|closed|all)
  • assigned_to=(username|none|all)
  • issuetype=("Bug report"|"Feature request"|Enhancement|Task|"User story"|Idea) -- or whatever types you have defined. Run ./tbg_cli help remote:list_issues in your TBG root directory to find out more.

How do I style the plugin's output?

We use a bunch of (hopefully distinctly named) classes on the elements we generate so you can style them using CSS. We recommend you use a child theme for that and similar theme extensions.

Fixed classes we use are:

  • debugbox -- for div elements that contain debug messages (only shown if WP_DEBUG is enabled)
  • errorbox -- for div elements that contain error messages
  • issue -- for span elements created by [issue] and [issues]
  • closed -- for span elements corresponding to a closed issue
  • open -- for span elements corresponding to an open issue
  • issuelist -- for ul elements created by [issues]
  • noissuelist -- for p elements created by [issues] if there are no issues to list
  • reportbug -- for a elements created by [reportbug]

Also, we insert a class to above mentioned span elements based on the respective issue's status. Using the default values of TBG you will get classes like new, confirmed, beingworkedon or readyfortestingqa. If in doubt, check the generated HTML.

How can I help?

You can

  • use The Bug Genie for WP,
  • vote on the WordPress plugin portal for it,
  • report bugs and/or propose ideas for improvement here and
  • blog about your experience with it.

Requires: 3.2.0 or higher
Compatible up to: 3.3.2
Last Updated: 5 years ago
Active Installs: Less than 10


0 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.