Sophie: bugzilla-4.4.12-1.mga5 noarch

bugzilla-4.4.12-1.mga5.noarch.rpm

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>3.12.&#160;Bug Status Workflow</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.12 Release"><link rel="up" href="administration.html" title="Chapter&#160;3.&#160;Administering Bugzilla"><link rel="prev" href="edit-values.html" title="3.11.&#160;Legal Values"><link rel="next" href="voting.html" title="3.13.&#160;Voting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.12.&#160;Bug Status Workflow</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="edit-values.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;3.&#160;Administering Bugzilla</th><td width="20%" align="right">&#160;<a accesskey="n" href="voting.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="bug_status_workflow"></a>3.12.&#160;Bug Status Workflow</h2></div></div></div><p>
      The bug status workflow is no longer hardcoded but can be freely customized
      from the web interface. Only one bug status cannot be renamed nor deleted,
      UNCONFIRMED, but the workflow involving it is free. The configuration
      page displays all existing bug statuses twice, first on the left for bug
      statuses we come from and on the top for bug statuses we move to.
      If the checkbox is checked, then the transition between the two bug statuses
      is legal, else it's forbidden independently of your privileges. The bug status
      used for the "duplicate_or_move_bug_status" parameter must be part of the
      workflow as that is the bug status which will be used when duplicating or
      moving a bug, so it must be available from each bug status.
    </p><p>
      When the workflow is set, the "View Current Triggers" link below the table
      lets you set which transitions require a comment from the user.
    </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="edit-values.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="administration.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="voting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.11.&#160;Legal Values&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;3.13.&#160;Voting</td></tr></table></div></body></html>