Create and Edit Releases

A release is a mid-range unit of time for planning and tracking. Consecutive iterations build towards larger goals or themes set out in a release. Releases deliver incremental user functionality and enhance the software solution to ensure an ongoing fit with customer needs.

Scrum masters, product owners, and other organizers create releases and modify their fields. Many teams use a quarterly release cadence, with 4 releases per year. Within each release are 4-6 iterations. During the Release Planning meeting, the entire team commits to a plan of work to be executed in an upcoming release.

Create and edit releases includes the following:

Manage releases

Organizers can create, edit, and delete releases from the Timeboxes page.

Your ability to create, edit, or view an iteration is dependent upon the user role and permissions you have been assigned for the project.

Use the Timeboxes page to find information about your releases, such as:

  • Release Date: The targeted date for the end of the release cycle.
  • Planned Velocity: The amount of estimate units the team anticipates they can complete in the release.
  • Task Est: The roll-up of the task detail estimates for all of the tasks assigned to the release.
  • To Do: The cumulative remaining amount of work units to be completed for all tasks in the displayed release.
  • Actual: A roll-up from all tasks which accumulates the true time the tasks assigned to this release took to complete. This is helpful for estimating future tasks.

Bulk create releases

If you use a project hierarchy, you can use bulk create to manage your releases. Bulk create allows you to create a single release and propagate it to all child projects of your current project. This saves time spent in configuration and makes it easy to establish shared schedules across child projects.

  1. Select the Plan tab, then select Timeboxes.
  2. Select Releases from the Type drop-down.
  3. Click the Add New button, and enter the name, start, and end dates.
  4. Click the Add with Details button.
  5. In the Create New Release editor window, select the Bulk Actions checkbox to publish your iteration to all child projects.
  6. Complete the other fields in the editor as necessary.
  7. Click Save.

In order to use the bulk create feature:

  • You must be in a parent project to use the Bulk Create field.
  • You can only create releases for those child projects for which you have create permissions.

When you use Bulk Create, the Release Name, Start Date, End Date, and State fields are automatically copied from the parent project release to the child project release.

Bulk update releases

If you use a project hierarchy, you can use bulk update to propagate edits made to the parent project to all related child projects. CA Agile Central tracks all linked child projects and updates specified fields to keep the entire project hierarchy in synch.

  1. Select the Plan tab, then select Timeboxes.
  2. Select the release you wish to edit. From the Gear menu, select Edit.
  3. In the Edit Release window, select one or both of the Bulk Actions checkboxes to publish your iteration to all linked child projects:
    • Update matching releasees in all child projects
    • Update Name and Release Date when changed in parent projects
  4. Complete the other fields on the editor as necessary.
  5. Click Save.

In order to use the bulk update feature:

  • You must be in a parent project to use the Bulk Actions fields.
  • You can only edit releases for those child projects for which you have update permissions.

When bulk update is activated, changes to the following fields are updated in the linked child projects:

  • Name
  • Start Date
  • Release Date
  • State

When editing a child project, the State field can be individually edited, but as long as the child project is still linked to the parent project through the Bulk Update field, any bulk update to the parent project will overwrite the individual edits.

Individual child projects can be unlinked from the parent project Bulk Update by deselecting the Bulk Update field. When deselected, the Name, Start Date, and Release Date fields are enabled. Make a change to any of these fields and from this point on, the child project release is unlinked and is not updated when bulk updates are made from the parent project.

Delete a release

Important! There is no recovery or revision history for deleted releases. If you delete a release that iterations are scheduled in, they will all be updated to unscheduled.

To delete a release:

  • Navigate to the PlanTimeboxes page.
  • Click the Gear icon next to the release you want to remove, and choose Delete.

Use the detail page

The Release detail page provides a view of an individual release.

From the Release detail page, you can:

  • Click any link in the sidebar to navigate to a summary page of the related work items of the indicated type.
  • Click the url URL icon in the upper-left corner of the detail page to open a New Release detail page with the complete URL to this work item. From here you can copy the URL to use as a reference link in an email to team members, attachments to other work items, and so on.
  • Use the Actions button to select options such as Edit, New, Copy, Print, Delete.

Release fields

Set these field values when creating or editing a release. Fields highlighted in red are required.

Field Description
Bulk Create Select this checkbox to apply this release to all child projects. This checkbox displays when you are in a parent project and create a new release. The release will be created using the same Name and End Date in all child projects of your current parent project.
Bulk Update Select this checkbox to allow edits made to the parent project release to be replicated for all child projects releases. Deselect from an individual child project release to remove its link from the parent project release and allow a unique edit or update to the child project release. This field displays only for a release that has the Bulk Create option enabled.
Name Enter the name of the release.
Theme Use this Rich Text Format field to enter a theme for your release.
Start Date Click the calendar icon and select the start date for the release from the resulting calendar.
Release Date Click the calendar icon and select the date which targets a release from the resulting calendar.
Version Enter an identifying version number for your release.
State Specify the current condition of the release. Valid values are:
  • Planning: The release is not yet active and is still being planned for future activity.
  • Active: The release is active and is currently in progress. If multiple releases have been defined with a state of Active, the release with the earliest start is considered the Active release.
  • Accepted: The release has met the release criteria.
  • Planned Velocity Specify the total number of points that the team thinks it can complete within this release. Although points is the recommended unit, you may customize the definition of units to indicate some other unit of measure.
    Project The current project for the release. This field defaults to the your current project and cannot be edited. To create a release in a different project, you must first switch to that project and then create the release.
    Plan Estimate, Task Estimate, Accepted, and To Do These totals are rolled up from the estimates given for the associated scheduled items and their tasks along with the actual number of units of remaining work to be done. The Accepted field calculates and displays the total of scheduled item estimates whose state have been set to accepted. These figures are presented to assist you in providing more accurate estimates for future releases. These fields are calculated in iteration units.
    Notes Record additional information associated with the release such as team decisions or discussion results.
    Change Description Record any changes made to the release during an edit. Comments are stored and displayed in the Revision History page.
    Note: Changes made to the release are also systematically captured for revision history.


    Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us at