Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bug 536183: Docs claim bug lifecycle is "hard-coded" despite that's no longer true

Browse Source 
r=gerv a=mkanat


git-svn-id: svn://10.0.0.236/branches/BUGZILLA-3_4-BRANCH@260757 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
mkanat%bugzilla.org 2010-07-13 23:27:04 +00:00
parent 80e7798c11
commit af5a259e14
2 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
mozilla/webtools/bugzilla/.bzrrev
View File

@ -1 +1 @@
6765
6766

10
mozilla/webtools/bugzilla/docs/en/xml/using.xml
View File

@ -365,10 +365,12 @@
<title>Life Cycle of a Bug</title>
<para>
The life cycle, also known as work flow, of a bug is currently hardcoded
into Bugzilla. <xref linkend="lifecycle-image"/> contains a graphical
representation of this life cycle. If you wish to customize this image for
your site, the <ulink url="../images/bzLifecycle.xml">diagram file</ulink>
The life cycle of a bug, also known as workflow, is customizable to match
the needs of your organization, see <xref linkend="bug_status_workflow"/>.
<xref linkend="lifecycle-image"/> contains a graphical representation of
the default workflow using the default bug statuses. If you wish to
customize this image for your site, the
<ulink url="../images/bzLifecycle.xml">diagram file</ulink>
is available in <ulink url="http://www.gnome.org/projects/dia">Dia's</ulink>
native XML format.
</para>