> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/agile-board-1/planning-board.md).

# Planning board

Within the planning board, you have the option to pull or push elements into your sprint. The project structure is displayed on the left-hand side, all your elements in the centre, and the active sprints on the right-hand side. You can push or pull different elements into your sprint by drag and drop. All elements are listed in the sprints. In order to push the elements out of the sprints, simply use the drag and drop functionality and drag it into the backlog items.

In the planning board, you get a better overview of which tasks are relevant to you by using filters. If you set a filter, the sprint elements will be displayed as grey squares. 

<figure><img src="http://aquawiki.andagon.com/pictures/drex_planning_board_rich_client_custom.png" 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.aqua-cloud.io/documentation/desktop-client/agile-board-1/planning-board.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.