When you link a CA Clarity™ PPM project to a CA Clarity™ Agile product, you can view and work with these products in CA Clarity™ PPM. After the projects are linked, if you update the project dates in CA Clarity™ PPM, the release dates are updated automatically in CA Clarity™ Agile.
The following table shows how CA Clarity™ Agile product and release fields map to CA Clarity™ PPM project fields:
|
CA Clarity™ Agile Fields |
CA Clarity™ PPM Fields |
|---|---|
|
Product Name |
Agile Product Name |
|
Product ID |
Agile Product ID |
|
Release Name |
Agile Release Name |
|
Release ID |
Agile Release ID |
|
Master Release ID |
Agile Master Release ID |
|
Start Date (release) |
Start Date (project) |
|
Release Date (release) |
Finish Date (project) |
When you add resources to the project team of the integrated CA Clarity™ PPM project, new accounts are created for users without Salesforce.com accounts. The resources are added as CA Clarity™ Agile users. Resources with existing Salesforce.com user accounts are added as CA Clarity™ Agile users and linked to the CA Clarity™ PPM project.
The employee number and email address for a resource is used to determine whether a Salesforce.com account exists for that resource.
When you mark a resource as inactive in CA Clarity™ PPM, the mapped Salesforce user also becomes inactive.
Create user stories and issues with tasks in CA Clarity™ Agile and assign them to sprints and releases (product, master, or both). Corresponding tasks are automatically created in the linked CA Clarity™ PPM project. Only user stories that are assigned to the master release display in the work breakdown structure if the CA Clarity™ PPM project is linked to a master release in CA Clarity™ Agile. All products that are associated to the master release appear at the top level.
The work breakdown structure of the CA Clarity™ PPM project tasks is built as follows:
If the CA Clarity™ PPM project is linking to a master release in CA Clarity™ Agile, the WBS hierarchy looks like the following:
Product – Release
Sprint
User Story
Task
Product – Release
Kanban Board
User Story
Task
If the CA Clarity™ PPM project is linking to a product release in CA Clarity™ Agile, the WBS hierarchy looks like the following:
Sprint
User Story
Task
Kanban Board
User Story
Task
When you enter the hours worked on a task in CA Clarity™ Agile using the Task Worklog or the Virtual Wall, the following updates occur in CA Clarity™ PPM:
The following table shows how CA Clarity™ Agile task worklog information maps to CA Clarity™ PPM timesheets:
|
CA Clarity™ Agile Worklog |
CA Clarity™ PPM Timesheet |
|---|---|
|
Agile User Name/Assigned To |
Resource Name |
|
Hours Worked |
Hours logged for one day |
|
Hours Remaining |
ETC |
|
Work Date |
A day in the timesheet time period |
|
Task Type |
Charge Code |
Each time you update your worklog in CA Clarity™ Agile, the corresponding timesheet is updated in CA Clarity™ PPM as long as the timesheet is not in submitted status.
You can delete your worklog in CA Clarity™ Agile even if time has already been populated in a CA Clarity™ PPM timesheet. If the timesheet is currently not submitted, it is updated based on the latest updates from CA Clarity™ Agile. If the timesheet is already submitted, create a timesheet adjustment.
When you create an impediment in CA Clarity™ Agile, the following updates occur in CA Clarity™ PPM:
The following table describes the fields that map to CA Clarity™ PPM and sync each time the Agile Sync job runs.
|
CA Clarity™ Agile Impediment Field/Value |
CA Clarity™ PPM Issue Field/Value |
|
Title (255 chars) |
Name (80 chars)* |
|
None, uses SFDC ID (18 chars) |
ID (18 chars) |
|
Description (32000) |
Description (250)* |
|
Assignee |
Owner |
|
Due Date |
Target Resolution Date |
|
Severity:
|
Priority:
|
|
Status:
|
Status:
|
This value truncates in CA Clarity™ PPM if the number of characters exceeds the CA Clarity™ PPM character limit.
|
Copyright © 2013 CA.
All rights reserved.
|
|