# Configuring the Agile Component

In order to configure the agile component, open the project configuration.  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_configuring_the_agile_component_rich_client_custom.png" alt=""><figcaption></figcaption></figure>

Here, you will find the fields Status for defects, requirements, test cases, test scenarios and scripts which can be elements of sprints. There are 4 columns: *Values, Default, Definition Of Done, Hide in sprints.* The Default field allows you to create a default status if a new element is created. This does not depend on the agile board. Furthermore, you have the options *Definition Of Done* and *Hide in sprints.*&#x20;

*Definition Of Done* is needed for the burn down diagram. If an element is shown in the status *Definition Of Done,* then the element is done and the burn down chart is decreasing.&#x20;

*Hide in sprints* is used to minimize your agile board. For example, if an element has the status *duplicate* and is set to *Hide in sprints*, it is not visible in the sprint board. Hence, you cannot set an element to the status duplicate via the sprint board.&#x20;

This configuration should be setup for all artefacts. If a status in one artefact has the same name as in another one, the status is merged. The status is only visible once in the agile module.&#x20;

Furthermore, you should insert the predefined fields *Sprint* and *Points* into the layout of each artefact.&#x20;

*Sprint* shows the related sprint. Points allows you to estimate the effort and to see the progress in a burn down chart.&#x20;

In order to mark requirements as *Task* or *User Story*, you need to add this as value for *Type* in the template for requirements.&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_configuring_the_agile_component_rich_client_custom_2.png" alt=""><figcaption></figcaption></figure>


---

# 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://docs.aqua-cloud.io/documentation/desktop-client/agile-board-1/configuring-the-agile-component.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.