🚀 JWT 3.0 is out 🚀 

The app was completely overhauled, and so was the documentation: Jira Workflow Toolbox (Server/Data Center) Home

The page you are viewing is still valid for all app versions prior to 3.0.

On this page

Example: Block an Epic's transition depending on linked issues status and due date

I have a task: Epic and Task. linked to the Epic to continue in a transition in the epic task, there is a validation: Only linked tasks containing: "Due date" filled and only jobs that are not closed (only open tasks and progress or other status).

Let us suppose that you want to allow a certain transition in Epic's workflow to be executed, only if all its tasks are unresolved and have Due Date set. In this case you can use the following boolean expression:

count(filterByPredicate(linkedIssues("is Epic of"), ^%{00028} != null OR ^{00012} = null)) = 0

Note that:

  • ^%{00028} is field code for "Resolution" in foreign issues
  • ^{00012} is code for numeric value of "Due Date" in foreign issues

There are many other posible boolean expressions, and also Validation on linked issues can be used.

Other variation of the usage example

When I own two tasks (type:"Demand") which must contain (compulsorily) the "Due date" field. This validation must be when all of the tasks of type: "Demand" having the field "Due date" filled.

The following validation is exactly the same as before, but only applies to "Demand" issues, i.e., issue types different from "Demand" does not have any requirement on Status or "Due Date":

count(filterByPredicate(linkedIssues("is Epic of"), ^%{00014} = "Demand" AND (^%{00028} != null OR ^{00012} = null))) = 0

This other validation is similar to the previous one, but restriction on Status applies to all issue types, while restriction on "Due date" only applies to "Demand" issues:

count(filterByPredicate(linkedIssues("is Epic of"), ^%{00028} != null OR ^%{00014} = "Demand" AND ^{00012} = null)) = 0

Note that:

  • ^%{00014} is field code for "Issue type" in foreign issues
  • The name of the issue type must be written exactly as it is, i.e., "Demand" should be the exact name of the issue type, respecting also the case

Other examples of that function

Related Usage Examples