Dependencies are work item relationships such as parent-child, predecessors, and successors. Identifying dependencies includes the following:
The CA Agile Central ribbon or
displays on a work item detail
. It organizes related work item links and makes them easy to access. Use the links to manage and navigate to listings of associated
for work items.
On a new editable detail page:
On a legacy detail page, such as
Your display of ribbon or sidebar links will vary depending upon the work item being viewed.
Each ribbon or sidebar link shows additional work items in reference to the displayed work item detail. A number displays, indicating the number of related work items regardless of any
view scoping applied.
||To go to...
||The detail page of the work item.
||A summary page of related children.
||A summary page of all projects associated to the currently viewed workspace. This page shows any parent-child hierarchies for the workspace.
||All user stories that must be completed before another user story can start or finish.
||All user stories that cannot start or finish until another user story is completed.
||All work items that depend on the displayed work item for implementation.
||All work items that the displayed work item depends on for implementation.
||A summary page of all tasks that are defined to implement the work item.
||Any defects that have been recorded against the displayed work item.
||All test cases for the displayed work item
||All related test cases including test steps for use in test execution.
||All test case results for the associated work item.
||A summary page of all discussion statements.
||A summary page of all attachments.
||A listing of all change revisions recorded for the displayed work item.
||A summary page of defect suites.
||A summary listing of duplicate defects.
||A listing of those defects that are contained within a defect suite.
||Displays a Story Burndown chart from the Story detail page.
An association is a term that implies a general type of relationship and is used to assist you in tracking and relating your work items. Each association is displayed in the ribbon or sidebar found on the work item detail page.
When deleting any work item that has
, you have multiple options for handling the associations. You may delete and remove the work item and its associations, continue with the delete and change the associations for the work item to none, or cancel the entire operation.
You can create a new test case
, log a
, or add an attachment from a test case. View these associations from the Test Case detail sidebar.
Defects allow you to create a test case. The test case will display on the Defect detail ribbon. Deleting the defect automatically removes the
, but the test cases remain intact.
Tasks are derived from
stories and defects, and can only be created from the
or defect. There is an automatic association between the user story or defect and the task. View these associations on the sidebar of the work item or the task. An individual task may be deleted with no effect on the work item.
In CA Agile Central, a parent-child relationship refers to a relationship between hierarchical projects, user stories, or test folders (requires CA Agile Central Quality Manager
). This relationship implies ownership. The parent owns its child projects or user stories. Parents can be decomposed into infinite levels of children. All parent-child relationships for projects and user stories are displayed in sidebar or ribbon of the related detail page. The parent-child
for test folders displays on the Quality Management page. Actions performed on the parent have implications on the children.
If a parent user story has been scheduled and a new child user story is added to the parent, the following actions take place:
- Tasks of a
are moved to the first
- Children inherit a copy of the values for
, Owner, and Blocked from their parent.
- Test cases and defects remain associated with the parent.
CA Agile Central uses predecessors and successors to indicate an ordinal relationship in which one user story is dependent upon the completion of another user story. By assigning a predecessor to an existing user story, an order is established between the two in which the successor user story is dependent upon functionality contained in the predecessor user story. Work should not begin on the successor user story until the predecessor user story is completed. User story states are rolled up to help you know when a predecessor is complete and work on a successor can begin. A blocked predecessor state is rolled up and easy to see from any User Story summary page.
In CA Agile Central you can:
- Create user story predecessors. You can create a new user story as a predecessor, or choose an existing user story. Creating a predecessor automatically indicates a successor.
- View all predecessors and successors from the User Story detail page.
- View the predecessors and successors for a user story from multiple summary pages such as the User Story,
, or Release Status pages.
- View the rolled up state of predecessors from the Successor User Story detail page.
- Receive email notifications when a predecessor or successor is changed.
Predecessors and successors can span projects within a
To view predecessors and successors on the Iteration Status and
pages, select the Show Columns icon and search for Dependencies. Select the checkbox next to Dependencies and select Apply.
The Dependencies column will then display on the page.
Each work item detail page contains a ribbon or sidebar, which displays all relationships to the current work item in a linked view. The ribbon or sidebar displays all possible associated work item types that are related to the current work item. Each link or icon is followed by a number in parenthesis indicating the number of associated work items that can be viewed in the resulting summary page.
On a new editable detail page:
On a legacy detail page, such as test case:
Select any association link or icon to navigate to the related work item summary page. The summary page offers all actions of the typical work item summary page. As you navigate through the related summary pages, the Actions button options vary in relation to the work item you are viewing.
On the legacy detail page, use the show and hide icons to control the sidebar display.
View the hierarchical tree from a child user story to its parent in a pop-up pane in the summary page from the user story ID.
You can add a predecessor user story to a new or existing user story. A predecessor user story is one whose implementation must be completed before work on another user story can begin.
To create a new user story as a predecessor to an existing user story:
The result is a new user story with a predecessor relationship from the current user story.
- From the Predecessors summary page, select Add New.
- Enter the name of the predecessor and select either Add or Add with Details. Enter any additional details as needed.
To create a predecessor relationship between two existing user stories:
- From the Predecessors summary page, select Choose.
- On the Choose Predecessors pop-up, check the user stories you wish to add and select Choose. You can select multiple predecessors.
- The chosen user stories display on the Predecessor summary page.
Predecessor-successor relationships are only allowed between user stories in the same workspace.
The User Story Predecessor summary page displays all user stories that must be completed before work can be initiated on the currently viewed user story. Use the Predecessors summary page to manage each user story's ordinal relationships.
From the User Story Predecessors summary page you can:
- Remove a predecessor user story by selecting the gear menu and selecting Remove. The user story remains intact.
- Edit a predecessor user story by selecting the gear menu next to the story and selecting Edit to view the editable detail page.
- Copy one predecessor user story to another new predecessor user story by selecting the gear menu next to the story and selecting Copy. The user story is copied and a predecessor implementation order is automatically set.
The User Story Successor summary page displays all user story successors that depend on the completion of another user story before work can be initiated on the currently-viewed user story. Use the Successors summary page to manage each user story's successor ordinal relationships.
From the User Story Successors summary you can:
- Edit a successor user story by selecting the gear menu and selecting Edit.
- Copy one successor user story to another new successor user story. The user story is copied and a successor implementation order is automatically set.
You can view a collection of all predecessors and successors and their states for a single user story as you work and plan from a summary page that displays user stories. This includes the following pages:
- User Story summary
- Release Status
- Predecessor or Successor summary
- Work item status
This allows you to view any relationships that impact your targeted user story without leaving your current page.
You can easily determine if your user story has a predecessor and successor by viewing the related icon in a user story row. When present, the following icons denote:
- The user story has one or more predecessors.
- The user story has one or more successors.
- The user story has both predecessors and successors.
Hover over any of the above icons to display a pop-up detail of the relationships. The resulting detail presents a header row containing the viewed user story, and two tabs that display predecessors and successors associated to the user story. From this pop-up you can also perform multiple activities.
Use the pop-up Successors tab to view those user stories that are awaiting completion of the current user story before work on them can begin.
View a rolled up state of the predecessors in the detail page of the user story.