Release and Development Policy Enforcement
The same workflow you use to automate issue processing in AccuWork is used to enforce release and development process policies in your AccuRev streams. In the StreamBrowser, you simply associate the workflow with the stream you want to control, and then specify the workflow rules you want enforced for that stream:
Setting workflow rules for a stream lets you:
- Specify whether or not you want to allow incomplete issues to enter the stream.
- Specify whether you want to use workflow rules exclusively when determining which issues can be in a stream, or whether you want workflow rules to apply only to issues of a specific type without preventing other issue types from entering the stream.
- Set workflow rules that restrict entry into and/or exit from a stream to issues in a given workflow stage. For example, you might want to restrict entry into your build stream to those issues whose status is Closed.
- Optionally perform a transition for issues when they enter or exit the stream.
By combining AccuRev’s streams-based SCM technology with the AccuWork issue-tracking system, workflow provides you with the tools you need to manage the issues, tasks, files, versions, and people associated with projects across the enterprise.
Workflows on Multiple Streams
You can use workflow on multiple streams in a depot. This allows you to define separate workflows, each with its own stages, transitions, and workflow rules, for different development efforts in your organization that are under AccuRev control. For example, you might want to define a workflow with one set of stages and transitions for new product development and another, with different stages and transitions, for the maintenance efforts associated with existing products. Multiple workflow support is ideal for development organizations that use separate streams to manage development efforts for new and existing software.