Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

On this page

Use case

Allow certain workflow transitions in "issue A" only if all their sub-tasks have a value on custom fields "user" and "date".

Configuration

Add the Logical validator to the desired workflow transition.

Expression

Add the following expression:

count(filterByPredicate(subtasks(), ^%{issue.cfnnnnn} != null and ^{issue.dueDate} != null)) = count(subtasks())

Replace ^%{issue.cfnnnnn} with the actual field code of the custom field.


Screenshots


Related use cases

Use caseJWT featureWorkflow functionParser functionsLabel
Block an Epic's transition depending on linked issues status and due date

Logical validator

Logical condition

count()

filterByPredicate()

linkedIssues()


Block an Epic's transition until all the issues under that Epic are resolved

Logical validator

Logical condition

count()

issuesUnderEpic()

filterByResolution()


Block a transition until all sub-tasks have certain fields populated

Logical validator

Logical condition

count()

filterByPredicate()

subtasks()

STAFF PICK

Ensure that all issues linked with a certain issue link type have "Due Date" field set

Logical validator

Logical condition

count()

linkedIssues()

fieldValue()


Ensure that an issue has at least one attachment

Logical validator

Logical condition

 

STAFF PICK

Evaluate Assets objects

Logical validator

Logical condition

findPattern() findReplaceAll() replaceAll() toStringList()


Halt a transition if an element is not contained in a list

Logical validator Logical condition

toStringList() 
Hide transition to a previous status

Logical condition 
Make "Time spent" field required

Logical validator



Prevent a closed issue from being reopened after resting 1 week closed

Logical validator

Logical condition

isInRole()
Prevent a transition depending of the number of components

Logical validator

Logical condition

numberOfSelectedItems()
Prevent external users from creating issues

Logical validator

matches() toString() textOnStringList() toStringList() userDisplayName() 
Prevent issue creation if description contains less than 100 characters

Logical validator

replaceAll() length() 
Prevent issue creation with the same field value (Boolean)

Logical validator

Validation based on JQL query

count()

issuesFromJQL()


Prevent setting due dates outside business hours

Logical validator

Logical condition

withinCalendar()

STAFF PICK

Prevent the creation of sub-tasks unless the parent issue is in a certain status

Logical validator

  
Reject duplicated file names in attachments

Logical validator

Logical condition

count()

toStringList()

distinct()


Restrict issue creation per issue type and project role

Logical validator

isInRole()
Set a condition in a global transition which only applies in a certain status

Logical condition 
Validate a Select List (cascading) custom field

Logical validator Logical condition

Validate only issue links created in transition screen

Logical validator

count()

transitionLinkedIssues()

filterByProject()

filterByIssueType()


Validation based on the value of a date type project property

Logical validator

Logical condition

stringToDate()

projectProperty()


If you still have questions, feel free to refer to our support team.