Limitations

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 Validator/Condition Limit

Jira only allows up to 3 validators or conditions from apps per transition. This is a platform-level limitation and cannot be changed.

Atlassian has rejected a request to raise this limit: JRACLOUD-82454

Need more than 3?

Use our Ultimate Validator – it lets you combine multiple checks into a single validator using a simple UI, with support for AND / OR logic between conditions.

Create issue transition

Team field

If you set up a Workflow Validator to verify if a value was chosen for the Team field (from Advanced Roadmaps) on a Create or Transition screen, it fails to function as the Jira expression does not detect the new value.

There is an open bug with Atlassian, which you can vote here: https://ecosystem.atlassian.net/browse/ACJIRA-2504

Description field

The issue's description field (Jira expression type - Issue) is expected to be of RichText type, which provides access to the plainText field for use in Jira expressions. However, during the "Create" transition (when a new issue is being created), the issue.description.plainText field is not accessible within a workflow validator. The description field becomes available for other transitions.

https://ecosystem.atlassian.net/browse/ACJIRA-2582

Parent field

When creating an issue, the parent field in Jira expressions is currently only available for subtasks, and for other issue types, it will always be null. This limitation affects our Validators, preventing them from detecting the parent issue—even if it is explicitly set in the Issue Create dialog.

There is an existing feature request for improved support of the parent field in Jira expressions—ACJIRA-2697. While the Atlassian Team has addressed some of the requested features, we have created a new request specifically tailored to this use case: https://jira.atlassian.com/browse/JRACLOUD-85039

Our Linked Issues Validator with the relation set to Parent is also affected by this limitation.

Linked Issues & Web Links

Currently, remote issue links (from other Jira instances) and web links cannot be validated using the Linked Issues Condition or Validator. This is due to a limitation in Jira Expressions, which do not expose remote or web links—they’re not returned in the issue.links property or anywhere else accessible.

✅ Local issue links (within the same Jira instance) are supported. ❌ Remote links and web links are not.

We’ve raised a feature request with Atlassian to address this: FRGE-1879 – Expose remote links in Jira Expressions.