Rate this page:
The jira:workflowCondition
module creates a workflow condition that can be configured on workflow transitions in
company-managed projects.
Conditions control whether the user can execute a transition. If a condition fails, the user won't be able to execute the transition. For example, the user won't see the transition button on the View issue page.
You can use Jira expressions to evaluate the condition result.
For example, a condition that checks if the issue is assigned would look like this:
1 2jira:workflowCondition: - key: my-forge-workflow-condition name: Issue is assigned condition description: This condition allows executing the transition if the issue has an assignee. expression: issue.assignee != null
A workflow condition only evaluates to true if the provided Jira expression evaluates to true. It will evaluate to false in all other cases, including when:
Property | Type | Required | Description |
---|---|---|---|
key |
| Yes |
A key for the module, which other modules can refer to. Must be unique within the manifest. Regex: |
name | string | Yes | The name of the condition displayed in the workflow configuration. |
description | string | Yes | The description of the condition, shown when adding the validator to a transition. |
expression | string | Yes | The expression used to evaluate whether or not the transition should be executed.
The expression should return a Boolean value. The expression is evaluated with the following context variables:
Additionally, these are available for Jira Service Desk transitions:
|
Whenever an app-registered Forge workflow condition
based on a Jira expression fails while executing, an avi:jira:failed:expression
event is sent.
You can subscribe to this event in Forge apps.
Rate this page: