Help:Bugzilla Extension: Difference between revisions
Jump to navigation
Jump to search
m (→How to Use) |
m (→How to Use) |
||
Line 22: | Line 22: | ||
Note that the tag name defaults to "bugzilla" but is configurable. | Note that the tag name defaults to "bugzilla" but is configurable. | ||
There is also exploratory support for charting: | There is also exploratory support for charting. Here are some examples: | ||
<pre> | <pre> | ||
<bugzilla type="count" display="bar"> | <bugzilla type="count" display="bar"> | ||
Line 31: | Line 33: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
</pre> | |||
This example uses date ranges and returns bugs from multiple products: | |||
<pre> | |||
<bugzilla type="count" display="bar"> | <bugzilla type="count" display="bar"> | ||
{ | { | ||
"product": ["Core","Calendar","Toolkit","Firefox | "product": ["Core","Calendar","Toolkit","Firefox"], | ||
"changed_after": "2000-01-01", | "changed_after": "2000-01-01", | ||
"changed_before": "2013-02-01", | "changed_before": "2013-02-01", |
Revision as of 23:00, 31 July 2013
Please add code samples and any additional tips on usage here:
How to Use
You use this extension in this way:
<bugzilla> (JSON REST API query key/value pairs) </bugzilla>
An example:
<bugzilla> { "product": "Bugzilla", "priority":"P1" } </bugzilla>
For more details on how to query in various ways, see the documentation for the Bugzilla REST API
Note that the tag name defaults to "bugzilla" but is configurable.
There is also exploratory support for charting. Here are some examples:
<bugzilla type="count" display="bar"> { "product": "Bugzilla", "priority": "P1", "x_axis_field": "severity" } </bugzilla>
This example uses date ranges and returns bugs from multiple products:
<bugzilla type="count" display="bar"> { "product": ["Core","Calendar","Toolkit","Firefox"], "changed_after": "2000-01-01", "changed_before": "2013-02-01", "whiteboard": "[good first bug]", "status":["NEW","REOPENED"], "x_axis_field": "product" } </bugzilla>