<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>2.6. Reports and Charts — Bugzilla 5.0.4 documentation</title>
<link rel="stylesheet" href="../_static/bugzilla.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '5.0.4',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true,
SOURCELINK_SUFFIX: '.txt'
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<link rel="shortcut icon" href="../_static/favicon.ico"/>
<link rel="search" title="Search" href="../search.html" />
<link rel="next" title="2.7. Pro Tips" href="tips.html" />
<link rel="prev" title="2.5. Finding Bugs" href="finding.html" />
</head>
<body>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="tips.html" title="2.7. Pro Tips"
accesskey="N">next</a></li>
<li class="right" >
<a href="finding.html" title="2.5. Finding Bugs"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="../index.html">Bugzilla 5.0.4 documentation</a> »</li>
<li class="nav-item nav-item-1"><a href="index.html" accesskey="U">2. User Guide</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="reports-and-charts">
<span id="id1"></span><h1>2.6. Reports and Charts<a class="headerlink" href="#reports-and-charts" title="Permalink to this headline">¶</a></h1>
<p>As well as the standard buglist, Bugzilla has two more ways of
viewing sets of bugs. These are the reports (which give different
views of the current state of the database) and charts (which plot
the changes in particular sets of bugs over time).</p>
<div class="section" id="reports">
<span id="id2"></span><h2>2.6.1. Reports<a class="headerlink" href="#reports" title="Permalink to this headline">¶</a></h2>
<p>A report is a view of the current state of the bug database.</p>
<p>You can run either an HTML-table-based report, or a graphical
line/pie/bar-chart-based one. The two have different pages to
define them but are close cousins - once you've defined and
viewed a report, you can switch between any of the different
views of the data at will.</p>
<p>Both report types are based on the idea of defining a set of bugs
using the standard search interface and then choosing some
aspect of that set to plot on the horizontal and/or vertical axes.
You can also get a form of 3-dimensional report by choosing to have
multiple images or tables.</p>
<p>So, for example, you could use the search form to choose "all
bugs in the WorldControl product" and then plot their severity
against their component to see which component had had the largest
number of bad bugs reported against it.</p>
<p>Once you've defined your parameters and hit <span class="guilabel">Generate Report</span>,
you can switch between HTML, CSV, Bar, Line and Pie. (Note: Pie
is only available if you didn't define a vertical axis, as pie
charts don't have one.) The other controls are fairly self-explanatory;
you can change the size of the image if you find text is overwriting
other text, or the bars are too thin to see.</p>
</div>
<div class="section" id="charts">
<span id="id3"></span><h2>2.6.2. Charts<a class="headerlink" href="#charts" title="Permalink to this headline">¶</a></h2>
<p>A chart is a view of the state of the bug database over time.</p>
<p>Bugzilla currently has two charting systems - Old Charts and New
Charts. Old Charts have been part of Bugzilla for a long time; they
chart each status and resolution for each product, and that's all.
They are deprecated, and going away soon - we won't say any more
about them.
New Charts are the future - they allow you to chart anything you
can define as a search.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Both charting forms require the administrator to set up the
data-gathering script. If you can't see any charts, ask them whether
they have done so.</p>
</div>
<p>An individual line on a chart is called a data set.
All data sets are organised into categories and subcategories. The
data sets that Bugzilla defines automatically use the Product name
as a <span class="guilabel">Category</span> and Component names as <span class="guilabel">Subcategories</span>,
but there is no need for you to follow that naming scheme with your own
charts if you don't want to.</p>
<p>Data sets may be public or private. Everyone sees public data sets in
the list, but only their creator sees private data sets. Only
administrators can make data sets public.
No two data sets, even two private ones, can have the same set of
category, subcategory and name. So if you are creating private data
sets, one idea is to have the <span class="guilabel">Category</span> be your username.</p>
<div class="section" id="creating-charts">
<h3>2.6.2.1. Creating Charts<a class="headerlink" href="#creating-charts" title="Permalink to this headline">¶</a></h3>
<p>You create a chart by selecting a number of data sets from the
list and pressing <span class="guilabel">Add To List</span> for each. In the
<span class="guilabel">List Of Data Sets To Plot</span>, you can define the label that data
set will have in the chart's legend and also ask Bugzilla to <span class="guilabel">Sum</span>
a number of data sets (e.g. you could <span class="guilabel">Sum</span> data sets representing
<span class="guilabel">RESOLVED</span>, <span class="guilabel">VERIFIED</span> and <span class="guilabel">CLOSED</span> in a
particular product to get a data set representing all the resolved bugs in
that product.)</p>
<p>If you've erroneously added a data set to the list, select it
using the checkbox and click <span class="guilabel">Remove</span>. Once you add more than one
data set, a <span class="guilabel">Grand Total</span> line
automatically appears at the bottom of the list. If you don't want
this, simply remove it as you would remove any other line.</p>
<p>You may also choose to plot only over a certain date range, and
to cumulate the results, that is, to plot each one using the
previous one as a baseline so the top line gives a sum of all
the data sets. It's easier to try than to explain :-)</p>
<p>Once a data set is in the list, you can also perform certain
actions on it. For example, you can edit the
data set's parameters (name, frequency etc.) if it's one you
created or if you are an administrator.</p>
<p>Once you are happy, click <span class="guilabel">Chart This List</span> to see the chart.</p>
</div>
<div class="section" id="creating-new-data-sets">
<span id="charts-new-series"></span><h3>2.6.2.2. Creating New Data Sets<a class="headerlink" href="#creating-new-data-sets" title="Permalink to this headline">¶</a></h3>
<p>You may also create new data sets of your own. To do this,
click the <span class="guilabel">create a new data set</span> link on the
<span class="guilabel">Create Chart</span> page. This takes you to a search-like interface
where you can define the search that Bugzilla will plot. At the bottom of the
page, you choose the category, sub-category and name of your new
data set.</p>
<p>If you have sufficient permissions, you can make the data set public,
and reduce the frequency of data collection to less than the default
of seven days.</p>
<hr class="docutils" />
<p>This documentation undoubtedly has bugs; if you find some, please file
them <a class="reference external" href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation">here</a>.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="../index.html">
<img class="logo" src="../_static/bugzilla.png" alt="Logo"/>
</a></p>
<h3><a href="../index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">2.6. Reports and Charts</a><ul>
<li><a class="reference internal" href="#reports">2.6.1. Reports</a></li>
<li><a class="reference internal" href="#charts">2.6.2. Charts</a><ul>
<li><a class="reference internal" href="#creating-charts">2.6.2.1. Creating Charts</a></li>
<li><a class="reference internal" href="#creating-new-data-sets">2.6.2.2. Creating New Data Sets</a></li>
</ul>
</li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="finding.html"
title="previous chapter">2.5. Finding Bugs</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="tips.html"
title="next chapter">2.7. Pro Tips</a></p>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="../search.html" method="get">
<div><input type="text" name="q" /></div>
<div><input type="submit" value="Go" /></div>
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="tips.html" title="2.7. Pro Tips"
>next</a></li>
<li class="right" >
<a href="finding.html" title="2.5. Finding Bugs"
>previous</a> |</li>
<li class="nav-item nav-item-0"><a href="../index.html">Bugzilla 5.0.4 documentation</a> »</li>
<li class="nav-item nav-item-1"><a href="index.html" >2. User Guide</a> »</li>
</ul>
</div>
<div class="footer" role="contentinfo">
Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.6.6.
</div>
</body>
</html>
