I don't remember having had to protect somehow UCM activity creation with special priviledge when using ClearQuest (we are no longer using it right now)
The IBM article "About creating UCM activities in a project enabled for Rational ClearQuest" summarizes the activity creation process: a user "work on a (ClearQuest) activity"
- An activity object is created in the stream to which the view is attached.
- The activity object is linked to the record in the Rational ClearQuest user database whose record type is enabled for UCM.
- The name of the Rational ClearCase activity is set to match the Rational ClearQuest record's ID.
You do not create UCM activity objects directly.
Since the creation of ClearCase UCM activities is managed by ClearQuest, you don't need to:
- create yourself some UCM activities
- try protect those by a specal owner.
You should rather use some policies like the WorkOn policy:
This policy is invoked when a developer attempts to set an activity.
The default policy script checks whether the developer’s user name matches the name in the Rational® ClearQuest® record Owner field.
If the names match, the developer can work on the activity. If the names do not match, the WorkOn fails.
The intent of this policy is to ensure that all criteria are met before a developer can start working on an activity. You may want to modify the policy to check for additional criteria.
The article "About Rational ClearCase activities and record types enabled for UCM" details the link between the two notions (UCM activities and ClearQuest record type)
In a project that uses the UCM integration with Rational ClearQuest, records based on a record type enabled for UCM can be linked with Rational ClearCase activity objects
This link enables the Rational ClearQuest client to display information about the Rational ClearCase activity (such as its change set, its stream, and whether it is currently set in any view).
The link also enables policies governing when you can deliver an activity in the Rational ClearCase environment and when you can close an activity in the Rational ClearQuest environment.
Because of the close association between linked UCM-enabled records and Rational ClearCase activities, the UCM documentation usually refers to both entities as activities.
At any point in a project, your Rational ClearQuest user database may contain records that are not linked to a Rational ClearCase activity object, but have a record type that is enabled for UCM.
For example, a newly created record might not be linked to a Rational ClearCase activity. You must explicitly complete an action (for example, by clicking Action > Work On
) to link such a record to a UCM activity.
However, each Rational ClearCase activity object in a project enabled for Rational ClearQuest must be linked to a Rational ClearQuest record.
You cannot create a Rational ClearCase activity object without linking it to a record in a Rational ClearQuest user database.
Tip: In a project enabled for Rational ClearQuest, a field is included to describe the activity owner. The Rational ClearQuest owner field and the Rational ClearCase activity creator are two different data points; the former is stored in a Rational ClearQuest user database and the latter in a Rational ClearCase PVOB.