Breaking Releases into Sprints or Sub-releases
• A sprint is a time-boxed unit of development used in the Scrum framework. In Codebeamer, a sprint belongs to a release. Therefore, every child of a release is a sprint in that release.
• Sprints have the same fields and workflow as their parent release, which are determined by the configuration trackerm.
• In the Release list, all sprints in a release are listed under their parent release. In the following example, release 2.0 has two sprints: 2.0-s1 and 2.0-s2.
• Sprint metrics (such as the number of outstanding or completed work items) are aggregated and therefore contribute to their parent release carry statistics.
• To create a sprint, click > on the Release Statistics page. You can then specify properties.
For each sprint, you can access the Planner, Cardboard, Release Dashboard, and Test Coverage pages using the icons in the top-right:
• You can include a release in another release by entering the release in the Release field of the other release. The statistics of both releases will be calculated recursively.
Associating Issues with Detected and Target Releases
After you submit your release to the Releases configuration tracker , you can associate work items with it. Set the Release fields of the issues to the release in which they will be addressed. You can set the Detected in fields to the release in which the issues were detected.
You can enter multiple releases in the Detected inand Release fields since an issue can be reported in multiple product versions and be fixed in multiple versions