Present issues from The Bug Genie in your WordPress blog.
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
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.
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:
issuetype=("Bug report"|"Feature request"|Enhancement|Task|"User story"|Idea)-- or whatever types you have defined. Run
./tbg_cli help remote:list_issuesin your TBG root directory to find out more.
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:
divelements that contain debug messages (only shown if
divelements that contain error messages
spanelements created by
spanelements corresponding to a closed issue
spanelements corresponding to an open issue
ulelements created by
pelements created by
[issues]if there are no issues to list
aelements created by
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
readyfortestingqa. If in doubt, check the generated HTML.