# Status and transitions

#### ➕ Adding Transitions

You can add transitions in two ways:

* **Drag & drop** from one status node to another
* Click **“Add Transition”** and select statuses

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

**Note:**

* Transitions open a sidebar only after being created.
* Transitions **cannot be edited**, only deleted and re-added.
* Delete transitions using the keyboard **Delete** key or the **sidebar icon**.

#### ⚡ Special Transition Type: **ANY**

Add a transition that applies to or from *any* status:

* **From \[status] → ANY**: move from one status to any other
* **From ANY → \[status]**: move from any status to one defined status

This is visually represented by special nodes on the graph.

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

### Transition Rules

In the **sidebar**, you can define two types of rules per transition:

#### **Status Transition Rule** (only one allowed)

Defines **which roles** can move an item from one status to another. Default is **Any role**.

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

#### **Advanced Rules** (multiple allowed)

Set field behaviors per role when the transition occurs. You can:

* Add/remove rules anytime
* See rule count directly on the transition arrow
* Edit or delete existing rules

<figure><img src="/files/1h652AiMk9f44tH9s4WB" alt=""><figcaption></figcaption></figure>

**Attributes of advanced rules:**

* **Field** – The field being impacted
* **Has Attribute** – What’s applied (e.g., Required, Read-only, Default Value)
* **Mode** (if applicable) – Define default value or empty state
* **For / Role** – Specify which roles are affected
* **Value** – Whether rules apply or not

Went there is at least one rules applied to Transition, then there is an indicator on the arrow, that shows that there are some rules.

<figure><img src="/files/u5C3eLq1Um3ZIWFMJ8GZ" 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/project-configuration/workflow-configuration/status-and-transitions.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.