Projects in CA Agile Central are primarily used to represent development teams. Team
, and work data is stored within these spaces. You can customize your projects by naming them after each team, identifying owners, and adding descriptions. CA Agile Central allows you to create a hierarchy of projects to represent multiple teams, scrums, or products which mirror your company development structure.
Setting up projects includes the following:
Projects are created from the
. Only users with
, workspace, or project administrator permissions can access this page.
To access the Workspace summary page:
From the Workspace summary page you can view all open projects in your workspace. Select the + icon to expand the workspace and any root level or parent projects and all open child projects are listed below the parent.
To view all projects (including closed projects) in the workspace, change the
drop-down from Open to All, and then select the Filter button at the top of the page.
You can also view all projects for a single workspace from the Workspace detail page. Select any workspace name in the summary page to navigate to the Workspace detail page. Select the Projects link from the sidebar on the left side of the page to display a projects summary view. From here you can:
- View a listing of all projects for the workspace. Click any project name to see the detail page.
- Perform the common actions of all work item summary pages.
Project Hierarchy Overview
CA Agile Central provides hierarchical projects in which a parent project can support up to 10 levels of child projects. This hierarchy is a tree structure with roll-up capabilities.
The project hierarchy supports an enterprise project structure in which you can match your CA Agile Central subscription to your company's organizational structure. You can use parent-child projects to represent internal company components such as:
- Product lines
- Projects (non-product)
A typical hierarchy looks like this:
The top-level parent project in the tree is often called by its organization or enterprise name. The next level down can be a product or portfolio container of work. At this level, you can see all of our teams within the product.
When you use a project hierarchy, there are additional benefits for your entire hierarchy. All summary pages cumulate totals and display
for all projects contained within your project
view. This helps you manage multiple projects and provides visibility into those team members who have responsibilities across multiple projects.
Child projects automatically inherit all
of the parent project.
Learn more about basic and complex project hierarchies.
Watch the Understanding the Project Hierarchy video to learn how project hierarchies enable powerful data roll-ups in CA Agile Central, and how to create and manage projects:
Create a Project
Creating a project is limited to subscription and workspace administrators. A workspace must have an open state for a project to be associated with it.
Projects cannot be deleted. Instead, edit the project and set the state to Closed. Once the project is closed it will remain intact, but will no longer display in the project drop-down list. Work items inside a closed project are not accessible.
Changes to projects are recorded in the revision history.
To view all projects (including closed projects) in the workspace, change the State drop-down from Open to All, and then click the Filter button at the top of the page.
To create a project:
The Projects summary page displays listing all projects contained within the workspace.
- In the Workspace summary page, select a workspace.
- Click the Projects link in the
- Click the Actions button and select New Project.
- In the Workspace summary page, locate the workspace to which you want to add the project.
- Click the Create Project for ... icon to access the New Project page.
|From a workspace
||From the workspace summary page
After your new project is created, the following flair message displays:
This message includes a link to the the Project User Access Grid where you can add users to your new project.
Create a Child Project
A child project is a subset of work to be done that is scheduled into releases and iterations. Create child projects to represent multiple teams, scrums, or products which mirror your company development structure. Create child projects from the Workspace summary page. Project administrators may create child projects under projects they administer.
To create a child project, begin from the Workspace summary page:
The New Project page displays. Use this page to define your new child project. The Parent field is automatically populated with the parent project name.
- Locate a workspace in which you want to work.
- Expand the workspace to locate the project to be designated as the parent project.
- Click the Add Project row icon.
- Select the Copy Timeboxes checkbox to copy current and future releases and iterations from the parent project.
- Select the Page Sharing checkbox to display shared custom pages from the parent project when viewing the child project.
- Click Save & Close.
Change Existing Projects to Child Projects
As your structure grows, you may need to change the hierarchy level of a project and make it a child project of another project. Projects must be in the same workspace.
To change existing projects to child projects:
- In the Workspace summary page, select a workspace.
- Click the Projects link in the sidebar.
- For the project you want to change, click the Edit icon.
- On the Edit Project page, click the magnifying glass icon in the Parent
- On the Choose Parent window, select the new parent project then click Choose.
View the Project Detail Page
The sidebar displays on the left side of the project detail page and is an easy way to identify and navigate to the specific work items that are associated to the displayed project. Use the sidebar links to access:
Click any displayed work item in the folder to navigate to its detail page.
Use the Actions button located at the top of the project detail to create a new project, edit, or print the displayed project.
Whether creating or editing a project, the same fields are presented as follows:
||Enter a project name. This field is a required field, but does not require a unique value.
||Specify whether the project is open or closed. An open project indicates the project is active and work can be performed on the related project components. A closed project has been completed or terminated and work can longer continue on any of the project components such as releases, iterations, or tasks.
||Select the owner of the project. This value defaults to the name of the administrative user who created the project.
||Click the magnifying glass icon to select a parent project. This field allows you to organize projects into parent-child hierarchies, or re-parent existing projects. Projects must be in the same workspace.
||This field is only available when you create a child project. Select this checkbox to copy current and future releases and iterations from the parent project. This option is checked by default. This is useful for reporting, planning, and tracking your releases.
||This field is only available when you create a child project. Select this checkbox to copy current shared custom pages from the parent project.
||This rich text format field provides a location for you to add any information that might be pertinent to the project. Link to URLs, insert a graphic, or provide any information that might help in further understanding the project's intent.
||This field only appears upon editing a project after it has been created. Log any information regarding any changes that have been made to the project's general information to provide a change history for the project.