Your suggestion would require us to add a new state to our workflow. In
our current design say for a defect record type, once a developer had
done his changes he typically transitions the record to "complete" (UCM
state type "complete") This does not mean that he's delivered his
changes. He may have been told to hold off delivering until some
date/event.
At this point the approval/final closure of the defect is up to the PM
types after code reviews, testing, etc...
Delivery however may occur at any point, in the defect record's life
cycle (opened, complete, reviewed, etc..) based on the project needs.
Note for example while the record is in the "opened" state checked in
files it can be delivered but this does not mean that the work is all
done. You would not automatically transition the record to complete as
you suggested. I guess the hook code could be restricted to transition
only records in certain states but that kind of negates the UCM policy
"Transition to Complete After Delivery". Based on these conditions it
would be difficult to indicate a "delivered" status on the CQ side.
As for the linking of the original defect record to the UCMUtility
record, this should be done by the Deliver action. A Parent-child type
of entry would do nicely in this regards.
Norm
Message: 9
Date: Tue, 18 Sep 2007 12:22:50 EDT
From: disadmin@us.ibm.com
Subject:
clearquest Re: Demos on what is coming in CQ
To: clearquest@lists.ca.ibm.com
Message-ID:
<1790314933.1190132601900.JavaMail.wassrvr@ltsgwas009.sby.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
You can do this today by how you configure the CQ workflow for UCM, and
by the UCM project policies. You can define a state in CQ that reflects
"Delivered", and map it to the UCM "complete" state type. In CQ, you
must have default state transitions for state types Waiting->Ready,
Ready->Active, and Active->Complete. These can map to whatever states
make sense in your CQ state model.
In the CC UCM project, you can select the policy "Transition to Complete
After Delivery" to have deliver activities automatically transitioned
from Active->Complete state types. This might map to Opened->Delivered
states in CQ, for example. This would give you the info in CQ that
tells you which tasks have been delivered.
If you want more automation than this, you can add code to the hook that
gets called when you select "Perform ClearQuest Action After Delivery".
I'm not sure linking the CQ activities to the deliver activity would
give you additional information, however. The deliver activity contains
the (union of the) change set of all the activities that were delivered,
but not the IDs of the activities themselves.
Leesa Hicks
Central Engineering, Software Services
Tektronix, Inc.
Regards,
Norm
_______________________________________________
clearquest mailing list
clearquest@lists.ca.ibm.com
Unsubscribe:clearquest-leave@lists.ca.ibm.com
