| 开发者 | akerbos87 |
|---|---|
| 更新时间 | 2012年2月25日 20:36 |
| PHP版本: | 3.2.0 及以上 |
| WordPress版本: | 3.3.1 |
[issue project=key issue=nr] -- prints a short link to the specified issue. If you add title=yes the issue title is printed, too.[issues project=key] -- prints a list of all issues of the specified project. See the FAQ for filtering options.[reportbug project=key] -- Prints a link the the specified project's report form. You can provide a custom link text as shortcode content, i.e. [reportbug project=key]My Text[/reportbug].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.
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.
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.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 messagesissue -- for span elements created by [issue] and [issues]closed -- for span elements corresponding to a closed issueopen -- for span elements corresponding to an open issueissuelist -- for ul elements created by [issues]noissuelist -- for p elements created by [issues] if there are no issues to listreportbug -- for a elements created by [reportbug]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.
You can