> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/workflow-building-blocks-for-jira/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/workflow-building-blocks-for-jira/administrator-guide/conditions-help.md).

# Conditions Help

Conditions Help is a panel that appears in the Activity section of Jira work items. It shows users which workflow conditions are configured for each transition and, where possible, whether they are currently met. This helps users understand why certain transitions may not be available.

## How it works

When a user views a work item, the Conditions Help panel displays all transitions that have conditions configured. For each transition, it breaks down every condition and shows whether it passes or fails based on the current state of the work item.

This is especially useful when:

* Users report that a transition button is missing and don't understand why
* Workflow administrators need to verify that conditions are working as expected
* Teams want transparency into what is required before a work item can move forward

## Enabling Conditions Help

Conditions Help is disabled by default. A Jira administrator must enable it from the app settings.

{% stepper %}
{% step %}

### Open the admin page

Navigate to **Jira Settings > Apps > Workflow Building Blocks for Jira - Conditions Help**.
{% endstep %}

{% step %}

### Enable the panel

Toggle **Enable Conditions Help panel** on. The panel will now appear in the Activity section for all users who have the **Transition work items** permission in the space.
{% endstep %}
{% endstepper %}

## Restricting access by role

By default, all users who can transition work items will see the Conditions Help panel. You can restrict visibility to specific space roles using the **Restrict to space roles** selector.

When one or more roles are selected, only users who belong to at least one of those roles in the given space will see the panel. Users outside the selected roles will see a message indicating the panel is restricted.

{% hint style="info" %}
Role restrictions apply to company-managed spaces only. In team-managed spaces, all team members with the Transition work items permission can see the panel regardless of the role restriction setting.
{% endhint %}

## What the panel shows

For each transition with conditions, the panel displays:

* **Transition name** and target status (color-coded by status category)
* **Availability badge** showing whether the transition is currently **Available** or **Restricted**
* **Condition tree** - the full structure of ALL/ANY groups and individual conditions
* **Status indicator** for each condition (see below)

Conditions are classified into three types:

| Type                       | Description                               | Evaluation                                                                    |
| -------------------------- | ----------------------------------------- | ----------------------------------------------------------------------------- |
| **App conditions**         | Conditions from Workflow Building Blocks. | Fully evaluated with pass/fail status.                                        |
| **Third-party conditions** | Conditions from other Forge apps.         | Evaluated if the condition exposes a Jira expression. Otherwise inconclusive. |
| **Native conditions**      | Built-in Jira conditions.                 | Shown but not yet evaluated. Support is being added gradually.                |

## Reading the panel

The panel lists every transition from the current status that has at least one condition configured. Each transition row shows the transition name, an arrow, and the target status.

By default, the panel uses a **simplified view** that collapses single-condition groups for a cleaner layout. You can switch to an **expanded view** using the toggle button to see the full condition tree with ALL/ANY group structure visible.

After making changes to a work item, use the **Refresh** button to re-evaluate all conditions against the updated state.

### Condition status indicators

Each condition displays a colored status dot:

| Color      | Meaning                                                                                             |
| ---------- | --------------------------------------------------------------------------------------------------- |
| **Green**  | Condition is met.                                                                                   |
| **Orange** | Condition is not met. This is likely why the transition is restricted.                              |
| **Red**    | The app encountered an error evaluating this condition. Expand the row to see details.              |
| **Gray**   | The app cannot automatically evaluate this condition. Common for native and third-party conditions. |

You can expand any condition row to reveal additional details such as the expression being evaluated or the condition configuration.

## Limitations

* The panel only shows transitions that have conditions configured. Transitions without conditions are always available and are not listed.
* Native Jira conditions are displayed but cannot be evaluated yet. They appear with a gray (inconclusive) status. Support for evaluating native conditions is being added gradually.
* Condition evaluation depends on the Jira REST API. If the API is temporarily unavailable, some conditions may show an error status.


---

# 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:

```
GET https://docs.forgappify.com/workflow-building-blocks-for-jira/administrator-guide/conditions-help.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.