> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/zephyr/execution-status-in-zephyr.md).

# Execution Status in Zephyr

1. Login to Zephyr with valid credentials

<figure><img src="/files/ogxJn0ePo5ENAsITXGY4" alt=""><figcaption></figcaption></figure>

2. From the landing page of Zephyr, select the **projects** you have chosen during the mapping process and select the same **release** you have chosen

<figure><img src="/files/w4HdHk9IR0hJElX45tiq" alt=""><figcaption></figcaption></figure>

3. Click Test Planning from the left vertical panel

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

4. After clicking on Test planning, you can see the releases on left pane of the window, next click release dropdown and click release which need to be mapped

<figure><img src="/files/HnCNcsHaYMVS0f3GQOCo" alt=""><figcaption></figcaption></figure>

5. After clicking release, the execution details of all the release functionalities that have been mapped with Zephyr will be visible

<figure><img src="/files/FcgZ0zGQXY4ftUsB6v5e" 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.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/zephyr/execution-status-in-zephyr.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.