This function has been renamed with the JWT 3.0 release.
Find the new documentation at:
Purpose
These condition and validator are among the most versatile tools in JIRA Workflow Toolbox, thanks to a powerful parser for boolean expressions. They allow writing complex conditions based on the value of one or more field values, using simple logic syntax with comparison operators and logical connectives AND, OR and NOT.
Logical expressions can contain Numeric, Date-Time and Text-String terms. Field values of most types can be referenced, including Cascading Select and Multi-Cascading Select. You can also introduce literal values (numbers, text strings, Dates-Time, logical values (true, false) and null).
A comprehensive set of functions and macros is available to operate on Date-Time, Number and Text-String terms.
The only difference between Boolean condition with math, date-time or text-string terms and Boolean validator with math, date-time or text-string terms, is that condition hides the transition where is inserted when the logical expression returns "false", and validator shows a custom message. In most cases the use of the validator is preferable than condition, since you can inform the user about the reason why he cannot execute the transition.
Example: Validate that there are still 2 days left to due date
In this example we implement a validation for checking that "Due date" has value at least 2 days greater than current date and time.
Note that:
- {00012} is code for numeric value of "Due date"
- {00057} is code for numeric value of "Current date and time"
Boolean condition with math, date-time or text-string terms and Boolean validator with math, date-time or text-string terms make use of the plugin's Expression Parser.
Collection of Boolean Expressions Examples
Usage Examples
- Block a transition until all sub-tasks have certains fields populated
- Block an epic's transition depending on linked issues status and due date
- Block or hide a transition for an issue depending on its issue links
- Block or unblock a transition after an issue rested a specific time in a status
- Block transition until all sub-tasks are in a specific status category
- Close parent issue when all sub-tasks are closed
- Enforce a field (Select List) to be set when another field (Radio Button) has a certain value (works with any kind of field type)
- Ensure that all issues linked with a certain issue link type have "Due Date" field set
- If field A is populated then, field B must also be populated
- Limit issue creation per role and issue type
- Limit the number of hours a user can log per day
- Limit valid dates for work logs
- Make "Time Spent" field required when there is no time logged in the issue
- Make a custom field mandatory when priority is "Critical" or "Blocker" and issue type is "Incident"
- Make attachment mandatory depending on the value of certain custom field
- Make different fields mandatory depending on the value of a Select List custom field
- Make linked issues, sub-tasks and JQL selected issues progress through its workflows
- Make parent issue progress through its workflow
- Prevent issue creation if another issue with same field value already exists
- Reject duplicated file names in attachments
- Require at least one sub-task in status "Resolved" or "Closed" when "Testing required" is selected in Check-Box custom field
- Require issue link when resolving as duplicate
- Restrict parent issue from closing if it has sub-tasks that were created during a given parent issue status
- Restrict sub-task type creation depending on parent issue status
- Restrict sub-task type creation depending on parent issue type
- Set a condition in a global transition which only applies in a certain status
- Validate a custom field "Story Points" has been given a value in Fibonacci sequence
- Validate compatible values selection among dependent custom fields
- Validate only issue links created in transition screen
- Validate that multi-user picker custom field A does not contain any user in multi-user picker custom field B
- Validation and condition based on time expressions
- Validation based on the value of a date type project property
- Validation on issue attachments
- Validation on MIME types of issue attachments
- Validation on sibling sub-tasks depending on issue type and status
- Validation on the value of a Cascading Select field