Set up a release
Set up releases in the relevant shared space or workspace, and define its timeline and workforce.
Shared space admin or workspace admin permissions are required.
This overview describes how to work with shared and non-shared releases.
Admins can define releases for:
All workspaces associated with a shared space.
The shared space admin creates and modifies these releases for a shared space. The release is then available to all associated workspaces.
For individual workspaces.
The workspace admin creates and modifies these releases for a specific workspace.
ALM Octane users working in a specific workspace can access both the releases defined for the corresponding shared space and also the releases defined specifically for that workspace.
Within a shared space or a workspace, release names must be unique. However a release defined for a shared space may have the same name as a release defined for the shared space's workspaces. To distinguish between the releases, ALM Octane displays the shared icon and non-shared icon accordingly.
Add the necessary releases before defining the timeline.
To add a release:
In Settings , click Spaces and select the shared space or workspace where you want to create a new release.
Releases can be defined on a shared space level and a workspace level. If defined on a workspace level, the release is only available for that workspace.
In the Releases tab, click Add Release.
Provide an appropriate name for the release. You can also add a description and attach documents.
Select the release type: Scrum or Kanban.
For Scrum releases, define start and end dates for the release and specify the duration of sprints in days or weeks.
ALM Octane adds the release and its details to the Releases grid.
Tip: To set the release as the default release, in the toolbar click the Set as Default Release button .
ALM Octane labels the default release as [Default] next to the release number in Backlog release filters, dashboard grids, and so forth. This lets you set rules to help you fill values according to a default.
After adding releases, edit the details of the release.
To update release details:
In Settings , click Spaces and select the shared space or workspace for the release. Then. click the release ID link to open the release.
Update the necessary details:
Edit global release details
In the Details tab of the release, change any of the following:
Start and end dates of the release
If you change the start or end dates of a release, ALM Octane adjust the release's existing sprints. ALM Octane updates sprint dates so the sprints run consecutively from the beginning of the release. ALM Octane also removes extra sprints are removed.
Add and edit sprints
In the Timelines tab, update details on the sprints.
When you open the Timeline tab for the first time, ALM Octane displays sprints based on the sprint length you specified when creating the release.
To create another sprint, in the toolbar, click . Then, in the Add Sprint dialog box, provide the sprint name, and start/end dates for the sprint.
If you are adding another sprint after the end of the release, make sure to select the Add as a last sprint (expand release) check box. This adds the sprint to the end of the timeline and adjusts the release calendar.
To edit sprint start and end dates, select a sprint block in the timeline and click . In the Sprint details box, update the name, sprint start/end dates, and the assigned teams for that sprint.
Add and edit milestones
A milestone is a significant date that occurs during the release timeline. This can include things such as Code Freeze, Regression End, and so on. Adding milestones lets you see where these dates fall relative to your sprints.
To add a milestone, click and provide the milestone name and date. To edit milestone details, select the milestone in the timeline and click .
Add and edit teams
In the Teams tab, click Assign teams.
Select the teams to assign and click Add.
By default, when you assign a team to a release, ALM Octane assigns the team to all the release's sprints.
If you later need to update the list of teams assigned to a sprint:
In the Timeline tab, select a sprint and click in the toolbar.
In the Sprint details dialog box, in the Teams drop-down list, select the teams.
Note: You can select only teams that are already assigned to this sprint's release.
Enter the estimated velocity for a team
For each team, you should enter the estimated velocity. Velocity is the number of story points you expect each team to finish during a sprint.
- In the Teams tab of a release, click the numerical ID link for a team. The team details open for that team.
In the Details tab the team, in the estimated velocity field, enter the estimated number of story points.
Note: This change is reflected for all releases for the team.
- Click Save.
ALM Octane displays the updated velocity in the Estimated velocity column of the Teams tab. ALM Octane also displays the number for the velocity in the Release Expected Capacity table in the Timeline tab.
In addition to using release names or numbers, you can use the idea of the current or default release.
ALM Octane defines the current release based on the dates you enter for each release.
Set the default release automatically or manually:
By default, ALM Octane sets the default release as the current release.
To override the default release from the current release, set the default in the release list. For example, if you have a favorite created to monitor all defects from the default release, at the end of a release timeline - when your developers have moved on to working on the next release - you can override the default release to view details from the previous release instead of the current one.
In filters, ALM Octane displays the default release with brackets as [Default release].
When you finish working on a release, you can deactivate it. Deactivated releases no longer appear on lists of data entry, such as assigning content to a release. However they do appear in filters, so you can see which content was assigned to obsolete releases.
Select one or more releases in the Releases grid, and click Deactivate Release .