> For the complete documentation index, see [llms.txt](https://docs.simplifyqa.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplifyqa.ai/release-and-sprints/introduction-to-releases.md).

# Introduction to Releases

### What is a Release?

In SimplifyQA, a Release represents a planned deployment of software that includes a set of features, enhancements, and bug fixes. Releases help teams manage the software development lifecycle efficiently by tracking progress, organising work, and ensuring timely delivery.

**Key Features of Releases in SimplifyQA**

* Plan and Track: Organise features and user stories into releases for better tracking.
* Traceability: Link requirements, test cases, and defects to a release for end-to-end visibility.
* Sprint Integration: Associate releases with sprints to align with Agile methodologies.

**Accessing the Releases Module**

* From the User Navigation Panel, go to Release Management ▶ Releases.

<figure><img src="/files/8XBipP0itod7UzCJSof6" alt=""><figcaption></figcaption></figure>

* The Releases page will open, displaying a list of existing releases with details like status, associated sprints, and version numbers.

<figure><img src="/files/2iw46DSOAJfHDYKTz2jw" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.simplifyqa.ai/release-and-sprints/introduction-to-releases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.