Set up a release

Workspace admin permissions are required.

A release contains a set of application changes that will be available for distribution at the same time. You create a release in the relevant workspace and define its timeline and workforce.

After you assign user stories and defects to the release, you can plan and track its progress to ensure timely completion.

See a slideshow overview!

Add releases

  1. In Settings , click Workspaces and select the workspace where you want to create a new release.

  2. In the Releases tab, click Add Release.

  3. Provide an appropriate name for the release. You can also add a description and attach additional documents.

  4. Select the release type: Scrum or Kanban.

  5. For Scrum releases, define start and end dates for the release and specify the duration of sprints in days or weeks.

  6. Click Add.

The release and its details are added to the Releases grid.

Tip: If you would like to set the release as the default release, select a release and in the toolbar, click the Set as Default Release button .

The default release is shown as [Default] next to the release number in Backlog release filters, dashboard grids, and so forth. This enables you set rules that will help you fill values to a specific default.

Back to top

Modify release information

Edit a release in the Workspaces > Releases settings page.

Click the release ID link to open the release you want to edit.

In the release details:

Edit global release details

In the Details tab of the release, change any of the following:

  • Start and end dates of the release

  • Release descriptions

Note: If you change the start or end dates of a release, the release's existing sprints are adjusted accordingly. Sprint dates are updated so the sprints run consecutively from the beginning of the release, and 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 automatically displays sprints based on the sprint length you specified when creating the release.

  • To create an additional 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 an additional 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 accordingly.

  • 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 enables you to see where these dates fall relative to your sprints when viewing the release timeline.

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
  1. In the Teams tab, click Assign teams.

  2. Select the teams to assign and click Add.

    By default, when you assign a team to a release, the team is assigned to all of the release's sprint.

If you later need to modify the list of teams assigned to a sprint:

  1. In the Timeline tab, select a sprint and click Edit Sprint in the toolbar.

  2. 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. This velocity is the number of story points you expect each time to finish during a sprint, based on performance over time of the team.

  1. In the Teams tab of a release, click the numerical ID link for a team. The team details open for that team.
  2. 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.

  3. Click Save.

The updated velocity is reflected in the Estimated velocity column of the Teams tab. The number for the velocity is also reflected in the Release Expected Capacity table in the Timeline tab.

Back to top

Release definitions

When you work with releases throughout ALM Octane, in addition to using the release names or numbers, you can also use the idea of the current or default release.

ALM Octane defines the current release based on the dates you enter for each release.

The default release can be set automatically or manually:

  • By default, ALM Octane sets the default release is the current release.

  • If you need to manually override the default release from the current release, you can set this 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.

Then, in filters, the default release is displayed with brackets as [default release].

Back to top

See also: