# Platform Limitations

The **Workflow Building Blocks for Jira** app relies heavily on features provided by **Jira Expressions**. If a capability is **not supported in Jira Expressions**, it will not be available in our conditions or validators.

Some known platform limitations are listed below. If you are affected, consider **commenting on and voting for** the linked Atlassian feature requests. This helps Atlassian prioritise missing functionality.

## Only company-managed projects

Conditions and Validators offered by apps are solely compatible with **company-managed** projects. The Jira platform does not support third-party workflow extensions in team-managed projects.

## App Validators and Conditions limit

In the **new workflow editor**, Jira no longer enforces the limit of 3 app-based validators or conditions per transition.\
This limitation still applies only when using the **old workflow editor**, which Jira is gradually phasing out.

**Need to combine multiple checks?**

If you need to consolidate several conditions or validation rules into a single step, you can use [Ultimate Validator](/workflow-building-blocks-for-jira/conditions-validators/ultimate.md) — it lets you combine multiple checks into one validator through a simple UI, with support for **AND / OR** logic between conditions.

## Create issue transition

Jira Expressions have gaps during the **Create issue** transition. These affect validators and conditions.

<table data-header-hidden><thead><tr><th width="154.11328125"></th><th width="426.10546875"></th><th></th></tr></thead><tbody><tr><td><strong>Field / Context</strong></td><td><strong>Limitation</strong></td><td><strong>Atlassian Reference</strong></td></tr><tr><td><strong>Team</strong> (Advanced Roadmaps)</td><td>A validator cannot detect a newly selected Team value during issue creation. Jira Expressions do not pick up the value from the Create or Transition screen.</td><td><a href="https://ecosystem.atlassian.net/browse/ACJIRA-2504">ACJIRA-2504</a></td></tr><tr><td><strong>Description</strong></td><td>During issue creation, <code>issue.description.plainText</code> is not accessible to workflow validators. This value becomes available only in later transitions.</td><td><a href="https://ecosystem.atlassian.net/browse/ACJIRA-2582">ACJIRA-2582</a></td></tr><tr><td><strong>Parent</strong></td><td>The <code>parent</code> field in Jira Expressions is available only for subtasks during creation. For other issue types, it is always <code>null</code>, preventing detection even if a parent is set in the Create dialog. Our <a href="/pages/FnwVjryfF4GOW80rGwjT">Linked Issues Validator</a> using the <em>Parent</em> relation is also affected.</td><td><a href="https://jira.atlassian.com/browse/JRACLOUD-85039">JRACLOUD-85039</a>, <a href="https://ecosystem.atlassian.net/browse/ACJIRA-2697">ACJIRA-2697</a></td></tr><tr><td><strong>Request Type</strong></td><td>Always returns <code>null</code> during creation in Jira Expressions, causing validators to fail when checking for a Request Type value.</td><td><a href="https://ecosystem.atlassian.net/browse/JSDCLOUD-12438">JSDCLOUD-12438</a></td></tr><tr><td><strong>Issue Status</strong></td><td><code>issue.status</code> is always <code>null</code> when evaluated by workflow validators on the Create Issue screen. Status-based checks cannot be performed at create time.</td><td><a href="https://ecosystem.atlassian.net/browse/FRGE-1885">FRGE-1885</a></td></tr><tr><td><strong>Transition</strong></td><td><code>transition.to.id</code> always returns the default status ID during issue creation, even if the user selects a different status.</td><td><a href="https://ecosystem.atlassian.net/browse/FRGE-1886">FRGE-1886</a></td></tr></tbody></table>

## Linked Issues & Web Links

The **Linked Issues Condition and Validator** cannot validate **remote issue links** (links to other Jira instances) or **web links**.

**Reason:** Jira Expressions do not expose remote or web links—they are not available via `issue.links` or any other accessible property.

| **Link Type**                             | **Support Status** |
| ----------------------------------------- | ------------------ |
| Local issue links (same Jira instance)    | ✅ Supported        |
| Remote issue links (other Jira instances) | ❌ Not supported    |
| Web links                                 | ❌ Not supported    |

A feature request has been raised with Atlassian to expose remote links in Jira Expressions: [FRGE-1879](https://ecosystem.atlassian.net/browse/FRGE-1879).


---

# 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.forgappify.com/workflow-building-blocks-for-jira/testing-and-debugging/limitations.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.