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 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
A similar request is tracked here: FRGE-1870
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
Jira Expressions have gaps during the Create issue transition. These affect validators and conditions.
Field / Context
Limitation
Atlassian Reference
Team (Advanced Roadmaps)
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.
Description
During issue creation, issue.description.plainText is not accessible to workflow validators. This value becomes available only in later transitions.
Parent
The parent field in Jira Expressions is available only for subtasks during creation. For other issue types, it is always null, preventing detection even if a parent is set in the Create dialog. Our Linked Issues Validator using the Parent relation is also affected.
Request Type
Always returns null during creation in Jira Expressions, causing validators to fail when checking for a Request Type value.
Issue Status
issue.status is always null when evaluated by workflow validators on the Create Issue screen. Status-based checks cannot be performed at create time.
Transition
transition.to.id always returns the default status ID during issue creation, even if the user selects a different status.
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.
Last updated