Previous Topic: Create Product Releases

Next Topic: Delete a Release

Edit Product Releases

After a product release is created, a user with super user or administrative privileges can modify any of its properties such as the start and end dates of a release. When editing the start and end dates of a product release, verify that they fall outside the start and end dates of all sprints in that release.

When you change the release date for a product, the burndown and velocity are recalculated for the altered number of days. The charts on Sprint Detail and Dashboards pages update accordingly.

Follow these steps:

  1. Access the Release Edit page in one of the following ways:
  2. Change the following fields, and click Save.
    Release Name

    Specifies the name of the new release.

    Limits: 80 characters

    Start Date

    Specifies the starting date for the release. To ensure the best burndown data for your release, this date must be at least as early as the start date of the first sprint in the release.

    Required: Yes

    Format: m/d/yy

    Active

    Specifies whether the release is active. Inactive releases do not appear as options in the filters throughout CA Agile Vision.

    Default: Active

    Master Release

    Defines the master release to which this release is associated. If the product has been associated with a master release, you can select a master release for this release.

    When you associate a product release to a master release, all user stories from all products in the product release automatically associates with the master release. If you do not want all user stories in a product release to assign automatically to the master release, associate individual products to the master release. You can then select which user stories from which products you want to assign to the master release.

    Product

    Specifies the unique name of the product.

    Required: Yes

    Release Date

    Specifies the delivery date for the release. The release date and start date can be the same. To ensure the best burndown data for your release, ensure that this date is at least as late as the end date of the last sprint in the release. Teams who do not know the release date when they start a release can update the release date as new sprints are added.

    Format: m/d/yy

    Description

    Defines the purpose of the object and provides additional relevant information.

    Limits: 255 characters