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 11 Next »

This condition can hide a transition based on the state and the number of an issue's sub-tasks.

The condition only makes sense when used in a workflow used by standard issue types.

You can specify multiple filter criteria that will be "and concatenated". Each sub-task that matches the combination of all criteria will be counted. 

The condition will pass if the number of counted sub-tasks is between a minimum and maximum boundary which can be separately specified. 

Configuration

Filter by issue type

Only sub-tasks with the selected issue types will be counted.

If you want to skip this filter, leave the selection empty and check the additional option Allow unselected issue types.

Filter by status

Optionally limit the sub-tasks to be counted by their status.

If you want to skip this filter, leave the selection empty and check the additional option Allow unselected statuses.

Filter by resolution

Optionally limit the sub-tasks to be counted by their resolution.

If you want to skip this filter, leave the selection empty and check the additional option Allow unselected resolutions.

Filter by field value

Optionally limit the sub-tasks to be counted by their field values. To achieve this you must enter an expression in Logical mode. The expression must return  true or false. 

Examples: 

ExpressionDescription
%{seed.issue.assignee} != null

Unassigned sub-tasks will not be counted. 

Values in sub-tasks have to be referenced by their seed field codes.

%{issue.dueDate} <= %{seed.issue.dueDate}

Only sub-tasks with a due date of equal to or later than the current issue's due date will be counted.

Values in sub-tasks have to be referenced by their seed field codes.

Minimum number of sub-tasks

Specify the minimum number of the counted sub-tasks that need to satisfy the specified filter criteria. The default value is 0.

Maximum number of sub-tasks

Specify the maximum number of the counted sub-tasks that need to satisfy the specified filter criteria. The default 1000.

If you set this number to 1, the condition will fail as soon as more than one sub-task satisfies the specified filter criteria.

Additional options

Optionally select one or multiple filters that should be ignored.

OptionDescription

Sub-tasks of unselected issue types will be counted regardless of their state (type, status, resolution, field values).

This option must be checked, if the issue type filter should be ignored.

Sub-tasks in unselected statuses will be counted regardless of their state (type, status, resolution, field values).

This option must be checked, if the status filter should be ignored.

This option must be checked, if the status filter should be ignored.


Sub-tasks with unselected resolutions will be counted regardless of their state (type, status, resolution, field values).

This option must be checked, if the resolution filter should be ignored.

Sub-tasks not matching the defined field values will be counted regardless of their state (type, status, resolution, field values).

This option must be checked, if the field value filter should be ignored.


Use cases and examples

Title
No content found.

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