|
|
|
Terminology in CA Clarity PPM and in CA Clarity Agile and CA Clarity Requirements varies slightly for the same object. A project in CA Clarity PPM is known as a release in CA Clarity Agile and CA Clarity Requirements.
Before you can share information, associate a CA Clarity PPM project with CA Clarity Agile and CA Clarity Requirements. Once you establish the association, the Agile and Requirements subpage in CA Clarity PPM becomes available for you to specify CA Clarity Agile or CA Clarity Requirements product and release details.
If you delete an associated CA Clarity PPM project, you cannot link another project to the same CA Clarity Agile or CA Clarity Requirements release. You can link a new CA Clarity PPM project to another release and can move the details (user stories, tasks, or requirements) to the newly linked release.
When the integration is complete, jobs that run in CA Clarity PPM update and synchronize information in CA Clarity PPM, CA Clarity Agile, and CA Clarity Requirements. The jobs that run depend on the information that is being updated. You can set the jobs to run periodically, or you can run them manually from CA Clarity PPM, as needed. For more information about jobs for this integration, see Jobs Management.
For a complete list of the fields that are updated between CA Clarity PPM,CA Clarity Agile and CA Clarity Requirements, see CA Clarity PPM Field Mapping for CA Clarity Agile and CA Clarity Requirements.
| Copyright © 2012 CA. All rights reserved. |
|