Record states and state transitions - Parsons Corporation
Record states and state transitions. Change requests move through a life cycle from submission through resolution. Each stage in this life cycle is called a state, and each movement from one state to another is called a state transition. Each state has specific actions associated with it.
ClearQuest State Diagram Rules - IBM
This technote provides a listing of general rules for creating state transitions in the IBM® Rational® ClearQuest® Designer, along with associated error messages. It also gives some examples for UCM enabled schemas.
You work with change request records by moving them through various stages, or “states.” In each state, you can perform actions such as modifying the record or moving it to another state. The Actions menu lists the actions that you can perform on the record while it is in any given state. Here’s an example of a typical workflow:
Using records to store change requests - clearquest.parsons.com
A record type is the layout or format for a particular type of change request. It defines the actions, fields, forms, behaviors, and possibly the state information associated with a record. Each record type is associated with its own state model, forms, and hooks, which control the collection and viewing of data for that type of change request.
Record types - Parsons Corporation
Rational® ClearQuest® software supports state-based and stateless record types. A state-based record type moves through a series of statuses or states (for example, Submitted, Assigned, Active, and Resolved), as a result of actions performed by users throughout the project.
Rational ClearQuest software can help you create repeatable, enforceable, predictable processes. Workflows are provided out of the box to jump-start your implementation. Workflows can also be easily customized with the ClearQuest Designer tool to meet your unique, specialized needs. States and actions can be defined, fields can
About Rational ClearQuest - IBM
Your Rational ClearQuest administrator can customize states and the actions associated with them. For example, in the default application, users are notified by e-mail when change requests are assigned to them. By setting up rules for state transitions, you can verify that your change requests are being thoroughly completed and tracked.
A ClearQuest schema contains the metadata that defines your workflow, that is, how your users work with records within ClearQuest. It includes record definitions, form and field definitions, record states and the actions that can be performed on records, and optional hook code that customizes your workflow.
Administering and Customizing ClearQuest - InformIT
A ClearQuest schema defines the process of working with a record, along with the Record form and relevant fields. Records have a variety of different states. The defect record begins in the Submitted state; from there you can change the state of the record to Closed, or you can modify the record without changing its state.
Rational ClearQuest - IBM
Rational ClearQuest MultiSite Provides distributed access to defect tracking and software change management processes through replication and synchronization repositories. ClearQuest and ClearQuest MultiSite Enables better insight, predictability and control of the software development process across geographically distributed environments.