About schema-specific actions

Your Rational® ClearQuest® database schema, which your project manager can customize, may support these common change request management actions:

• Marking activities as duplicate
• Reopening closed activities
• Postponing activities

Your database schema may provide various ways to use these actions. For example, record types that can be postponed may have a Postpone command that you can choose after clicking Actions in the Record form pane.

Keep the following concepts in mind concerning the UCM integration with Rational ClearQuest while using any schema-specific actions:

• Your project manager can set up each record type that is enabled for UCM to behave differently; some actions may not be available for all record types.
• You cannot move an activity to another development stream. However, you can move versions in an activity change set to another activity in the same stream or to an activity in a different stream.
• You cannot delete an activity that is either currently set in a view or that contains versions in its change set. The UCM View field in the ClearQuest Query results pane indicates whether an activity is currently set. The activity Change Set list, which is available from the ClearQuest Record form pane or from an activity's properties sheet, displays an activity's change set.
• It is risky to work in a development stream that contains activities you do not intend to deliver. Keeping undelivered activities in your development stream increases the risk that, after a rebase operation, your development stream does not contain a cohesive set of versions. To avoid this increased risk, if you begin working on an activity and then postpone it until the next release, move the work to the new project and then create and work in a new development stream.