After creating a release 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 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 project, the burndown and velocity are recalculated for the altered number of days. The charts on Sprint Detail and Dashboards pages update accordingly.
To edit release properties
Specifies the name of the new release.
Limits: 80 characters
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
Specifies whether the release is active. Inactive releases do not appear as options in the filters throughout Agile Vision.
Default: Active
Specifies the unique name of the product.
Required: Yes
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 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
Defines the purpose of the object and provides additional relevant information.
Limits: 255 characters
| Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |