About records
A Rational ClearQuest database
contains different types of records, as defined in the Designer.
You can use different types of records for different projects and purposes.
Each record type has unique fields and data requirements.
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.
Record types
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.
Creating and submitting records
You can create and submit records for all the record types defined
in the schema from the Rational ClearQuest Web
interface.
Using record templates
When you create many records with similar input, it is often useful
to create a record template for the associated record type. Then you can use
the record template to create new records that are populated with field values
that you use saved in the template.
Modifying a record
You can edit an existing record if at least one modify
action is defined in the schema.
Modifying multiple records using multirecord update
You can perform the same actions on multiple ClearQuest records in a query result set
by using the multirecord update feature. For example, you can perform
the Assign action to assign many defect records to the same person
for the same iteration. You can use multirecord update to set the
priority of multiple records to a single value.
Changing the state of a record
You can change the state of a state-based record if at
least one change-state action is defined in the schema.
Changing the state of multiple records
You can use the multirecord update feature to change the
state of multiple ClearQuest records
in a query result set.
Deleting records
If at least one delete action is defined in your schema
for a specific record type, you can delete a record of that record
type.
Duplicating records
If two records are similar, you can place one in a Duplicate
state. A record can be a duplicate of only one record, but it can
have more than one duplicate. For example, Record A can be a duplicate
of Record B, and Record C can be a duplicate of Record B.
Reverting the state of duplicate records
You can revert a duplicate record to the state it was in before
it was marked as a duplicate. Reverted records can be modified.
Running recent records, queries, reports, and charts again Rational ClearQuest Web
keeps a history of recently run records, queries, data-push reports,
and traditional data-push charts during your current user session
so that you can run them again.
Viewing and saving UCM change set versions
You can track the progress of development work associated
with a record by viewing the UCM change set versions. You can also
save the UCM change set versions to a text file.
Viewing recently accessed records Rational ClearQuest Web
keeps a history of the most recently accessed records only for your current
user session so that you can easily view them again.