CA Clarity PPM Field Mapping for CA Clarity Agile and CA Clarity Requirements › Task Mapping

Task Mapping

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 and CA Clarity Requirements. 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:

• The product name and release name appears as the top-level summary task with sprints, Kanban Board, user stories, or issues and tasks cascading below it.
• If user stories are not assigned to a product release but to a master release, the top-level summary task appears as the product name.
• If user stories are not assigned to a master release but to a product release, the top-level summary task appears as the release name.
• Assigned user stories are grouped under sprints or Kanban Board.
• Unassigned user stories are grouped as unscheduled tasks.
• Tasks are grouped under user stories to which they are associated.
• Issues are grouped under sprints, Kanban Board, or unscheduled tasks at the same level as user stories.

If the CA Clarity PPM project is linking to a master release in CA Clarity Agile and CA Clarity Requirements, 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 and CA Clarity Requirements, the WBS hierarchy looks like the following:

Sprint

User Story

Task

Kanban Board

User Story

Task