Summing Up: Results of Implementing a Workflow

Implementing a workflow for issues with the type of defect as described in this Quick Start has resulted in the following behavior:

• Only issues with a Type field whose value is set to defect come under the control of this workflow.
• For defects, the Issue Edit form displays buttons that identify the issue’s current workflow stage, and the transitions that can be executed from that stage.

  

  Clicking the stage button (here, it is New) displays a read-only version of the workflow diagram, providing users with an understanding of where their issue is relative to other stages in the workflow.

  Clicking a transition button (here it is to Scheduled, but there might be more than one) moves the issue through the workflow. The availability of a transition is based on the issue’s current stage and any conditions you have defined for the transitions, you might specify a condition that makes a particular transition available only to a specific user or group, for example.

  Finally, notice that the Status field is read-only. It can be updated only by AccuRev based on actions defined for the appropriate workflow stage or transition.

• In addition to issue automation, users can now use the workflow to filter query results based on the issue type specified in the workflow condition. Query results can be filtered further by workflow stage.
• Once the defects workflow is associated with a stream, only issues whose type is defect are allowed in that stream.
• Additional restrictions were defined for issues entering the stream, in the Quick Start example, only issues in the Done stage can be promoted into the QA stream.