# Releases

{% hint style="success" %}
This tutorial helps understand how Timebook handles the concept or Releases in product delivery.
{% endhint %}

In Timebook, releases combine the traditional definition of software release cycle with a wider strategic approach to product delivery. Depending if you're a Team Leader or a Product Manager, you could treat them as a final collection of items released in a development cycle, or a roadmap of features and user stories leading to a designated goal.

## Configuring releases

In order to use the sprints you must first activate them in your team settings under **Planning** → **Releases**.

## Working with releases

{% hint style="info" %}
In their assumptions, releases are similar to [sprints](https://help.timebook.ai/hc/get-started/delivery/sprints). If you have worked with sprints before, you should be comfortable with releases right from the start.
{% endhint %}

Contrary to Sprints which usually contain smaller-scale work items, Releases are thought as a broader container for larger objects. This might include features assigned to a specific goal, or a collection of items delivered in a sprint from several different teams.

For example, you can create a release that will include sprints from a back-end team, and a front-end team.

### Creating a release

{% stepper %}
{% step %}
Go to **Planning** → **Releases** and click 'Create first release'.
{% endstep %}

{% step %}
Enter the details of the Release: name, description, date range in which the release should be ready, team responsible, and the product it refers to:

<div align="left"><figure><img src="https://3284049081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCMXgzPoiE4UXP4jn6B8%2Fuploads%2Fgit-blob-e8e0ba237a58cea8f8f0c031f86df4e5418f4a7a%2FCleanShot%202025-09-04%20at%2015.11.37%402x.png?alt=media" alt="" width="563"><figcaption><p>New release configuration</p></figcaption></figure></div>
{% endstep %}

{% step %}
You can add more releases using the `+` button on the Releases overview tab:

<div align="left"><figure><img src="https://3284049081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCMXgzPoiE4UXP4jn6B8%2Fuploads%2Fgit-blob-5e1e6287a4118e22f50864c001e9eef087ed9c44%2FCleanShot%202025-09-04%20at%2015.29.08%402x.png?alt=media" alt="" width="563"><figcaption><p>Add button location for new sprints</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

### Adding items to releases

#### Method 1: Property

The most straightforward way to add an item to a release is by using the dedicated property in the right panel:

<div align="left"><figure><img src="https://3284049081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCMXgzPoiE4UXP4jn6B8%2Fuploads%2Fgit-blob-74a2b1ce5eb4217666a20376cc1c06c27e39ea9d%2FCleanShot%202025-09-04%20at%2015.48.40%402x.png?alt=media" alt="" width="563"><figcaption><p>Adding items to releases with properties</p></figcaption></figure></div>

#### Method 2: Drag and drop

Once your workload in Timebook grows, you can assign items simply by dragging and dropping them across lists of tasks grouped by the 'Release' property.

{% hint style="success" %}
This method is applicable to any selected property across the whole system.
{% endhint %}

{% stepper %}
{% step %}
First, you need to properly group work items on the list. Go to **Delivery** → **Work items** and click 'Manage view'.
{% endstep %}

{% step %}
Set grouping to **Release** and apply filtering and sorting as desired. On the example below, you can see items sorted by [item type](https://help.timebook.ai/hc/get-started/work-items#types-of-work-items) (bugs & user stories):

<div align="left"><figure><img src="https://3284049081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCMXgzPoiE4UXP4jn6B8%2Fuploads%2Fgit-blob-e37384644cd78a29f6a9d4727188fbf7a323e4e5%2FCleanShot%202025-09-05%20at%2009.33.52.png?alt=media" alt="" width="563"><figcaption><p>Grouping work items by releases</p></figcaption></figure></div>
{% endstep %}

{% step %}
Now you can grab tasks and drag them over to the desired release:

<div align="left"><figure><img src="https://3284049081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCMXgzPoiE4UXP4jn6B8%2Fuploads%2Fgit-blob-10270f2e8457d6f6344de1930f3d518877acc727%2FCleanShot%202025-09-05%20at%2010.15.25%402x.png?alt=media" alt="" width="563"><figcaption><p>Dragging items across releases</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

### Releases overview

The default view of Releases is timeline. It provides key information on the progress and items contained, together with a visual representation of the release cadence in the selected time frame.

<div align="left"><figure><img src="https://3284049081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCMXgzPoiE4UXP4jn6B8%2Fuploads%2Fgit-blob-70735ad22dea6ea2398c637dbc53e5fe3377939f%2FCleanShot%202025-09-05%20at%2010.34.46%402x.png?alt=media" alt="" width="563"><figcaption><p>Release details explains</p></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.timebook.ai/hc/get-started/delivery/releases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.