Limitiations
Last updated
Last updated
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.
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:
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.
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—. While the Atlassian Team has addressed some of the requested features, we have created a new request specifically tailored to this use case:
Our Linked Issues Validator with the relation set to Parent is also affected by this limitation.
In the new workflow editor, validators and conditions provided by third-party apps are currently not supported. Any existing ones are displayed as "Unavailable rule." To use them, please switch to the old editor.
To keep track of when support for third-party apps will be introduced for the new editor we have created a feature request: . Please vote and comment.