<!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.4. Editing a Bug — 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.5. Finding Bugs" href="finding.html" />
<link rel="prev" title="2.3. Understanding a Bug" href="understanding.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="finding.html" title="2.5. Finding Bugs"
accesskey="N">next</a></li>
<li class="right" >
<a href="understanding.html" title="2.3. Understanding a Bug"
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="editing-a-bug">
<span id="editing"></span><h1>2.4. Editing a Bug<a class="headerlink" href="#editing-a-bug" title="Permalink to this headline">¶</a></h1>
<div class="section" id="attachments">
<span id="id1"></span><h2>2.4.1. Attachments<a class="headerlink" href="#attachments" title="Permalink to this headline">¶</a></h2>
<p>Attachments are used to attach relevant files to bugs - patches, screenshots,
test cases, debugging aids or logs, or anything else binary or too large to
fit into a comment.</p>
<p>You should use attachments, rather than comments, for large chunks of plain
text data, such as trace, debugging output files, or log files. That way, it
doesn't bloat the bug for everyone who wants to read it, and cause people to
receive large, useless mails.</p>
<p>You should make sure to trim screenshots. There's no need to show the
whole screen if you are pointing out a single-pixel problem.</p>
<p>Bugzilla stores and uses a Content-Type for each attachment
(e.g. text/html). To download an attachment as a different
Content-Type (e.g. application/xhtml+xml), you can override this
using a 'content_type' parameter on the URL, e.g.
<code class="file docutils literal"><span class="pre">&content_type=text/plain</span></code>.</p>
<p>Also, you can enter the URL pointing to the attachment instead of
uploading the attachment itself. For example, this is useful if you want to
point to an external application, a website or a very large file.</p>
<p>It's also possible to create an attachment by pasting text directly in a text
field; Bugzilla will convert it into an attachment. This is pretty useful
when you are copying and pasting, to avoid the extra step of saving the text
in a temporary file.</p>
</div>
<div class="section" id="flags">
<span id="editing-flags"></span><h2>2.4.2. Flags<a class="headerlink" href="#flags" title="Permalink to this headline">¶</a></h2>
<p>To set a flag, select either <span class="guilabel">+</span> or <span class="guilabel">-</span> from the drop-down
menu next to the name of the flag in the <span class="guilabel">Flags</span> list. The meaning
of these values are flag-specific and thus cannot be described in this
documentation, but by way of example, setting a flag named <span class="guilabel">review</span>
<span class="guilabel">+</span> may indicate that the bug/attachment has passed review, while
setting it to <span class="guilabel">-</span> may indicate that the bug/attachment has failed
review.</p>
<p>To unset a flag, click its drop-down menu and select the blank value.
Note that marking an attachment as obsolete automatically cancels all
pending requests for the attachment.</p>
<p>If your administrator has enabled requests for a flag, request a flag
by selecting <span class="guilabel">?</span> from the drop-down menu and then entering the
username of the user you want to set the flag in the text field next to the
menu.</p>
</div>
<div class="section" id="time-tracking">
<span id="id2"></span><h2>2.4.3. Time Tracking<a class="headerlink" href="#time-tracking" title="Permalink to this headline">¶</a></h2>
<p>Users who belong to the group specified by the <code class="docutils literal"><span class="pre">timetrackinggroup</span></code>
parameter have access to time-related fields. Developers can see
deadlines and estimated times to fix bugs, and can provide time spent
on these bugs. Users who do not belong to this group can only see the deadline
but not edit it. Other time-related fields remain invisible to them.</p>
<p>At any time, a summary of the time spent by developers on bugs is
accessible either from bug lists when clicking the <code class="docutils literal"><span class="pre">Time</span> <span class="pre">Summary</span></code>
button or from individual bugs when clicking the <code class="docutils literal"><span class="pre">Summarize</span> <span class="pre">time</span></code>
link in the time tracking table. The <code class="file docutils literal"><span class="pre">summarize_time.cgi</span></code>
page lets you view this information either per developer or per bug
and can be split on a month basis to have greater details on how time
is spent by developers.</p>
<p>As soon as a bug is marked as RESOLVED, the remaining time expected
to fix the bug is set to zero. This lets QA people set it again for
their own usage, and it will be set to zero again when the bug is
marked as VERIFIED.</p>
</div>
<div class="section" id="life-cycle-of-a-bug">
<span id="lifecycle"></span><h2>2.4.4. Life Cycle of a Bug<a class="headerlink" href="#life-cycle-of-a-bug" title="Permalink to this headline">¶</a></h2>
<p>The life cycle of a bug, also known as workflow, is customizable to match
the needs of your organization (see <a class="reference internal" href="../administering/workflow.html#workflow"><span class="std std-ref">Workflow</span></a>).
The image below contains a graphical representation of
the default workflow using the default bug statuses. If you wish to
customize this image for your site, the
<a class="reference external" href="../../images/bzLifecycle.xml">diagram file</a>
is available in <a class="reference external" href="http://www.gnome.org/projects/dia">Dia's</a>
native XML format.</p>
<img alt="../_images/bzLifecycle.png" src="../_images/bzLifecycle.png" />
<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 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.4. Editing a Bug</a><ul>
<li><a class="reference internal" href="#attachments">2.4.1. Attachments</a></li>
<li><a class="reference internal" href="#flags">2.4.2. Flags</a></li>
<li><a class="reference internal" href="#time-tracking">2.4.3. Time Tracking</a></li>
<li><a class="reference internal" href="#life-cycle-of-a-bug">2.4.4. Life Cycle of a Bug</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="understanding.html"
title="previous chapter">2.3. Understanding a Bug</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="finding.html"
title="next chapter">2.5. Finding Bugs</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="finding.html" title="2.5. Finding Bugs"
>next</a></li>
<li class="right" >
<a href="understanding.html" title="2.3. Understanding a Bug"
>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>
