Previous Topic: Synch ServerNext Topic: Posting Hours to a Task


Package Associations

After the SCM Project is associated with a CA Vision Release, the CA Vision integration involves associating SCM Packages with CA Vision objects such as Requirements, User Stories, and/or Tasks. After a Package is associated with a CA Vision object, the following activities and operations are enabled:

  1. Package Activity - When a package is associated with a requirement, user story, or task, the package activity similar to the SCM package history is posted to the CA Vision object. This activity is displayed in the CA Harvest SCM package display segment of the requirement or user Story. All package operations such as Created, Approved, Promoted, and Demoted are logged to the CA Vision object.
  2. (Optional) Code Changes - When a package is associated with a requirement, user story, or task, the trunk item versions of that package are posted to that user story. When the package is promoted to the configured Development Completion state, the code changes are posted to the user story. If the package is demoted to a state previous to the Development Completion state, the code change records are removed from the user story. Similarly, when a switch package is executed, the code changes are removed from the user story.
  3. Posting Worklog Hours - If a package is associated with a task or a user story, the task worklog hours are posted using SCM Workbench. If the package is associated with a user story, then the user selects the task from the Tasks list. This list consists of the tasks that belong to the selected user story.
  4. (Optional) Automatic Task Status Update - If you enable this option for the SCM Project, an Implementation, Design, or Doc Task associated with the package is automatically updated to the Completed status when the package is promoted to the Development Completion state. If the package is later demoted out of this state, its status is returned to In Progress. Similarly, QA associated with an SCM Package is updated to the Completed status when the package is promoted to the QA Completion state.