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 15 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". Per default, all sub-tasks must match the combination of all criteria will be counted.  

Configuration

Filter by issue type

If you select specific issue types, all sub-tasks must be of any of the selected issue types. If subtasks with other issue types are found, the condition will fail.

The additional filters can be used to further restrict the state of the selected issue types.

If you leave this filter blank, e.g. if the issue type is irrelevant, you must check the additional option Allow unselected issue types. → Ignore issue type filter / issues in unselected issue types

If you select specific issue types and also check the additional option Allow unselected issue types, the additional criteria (status, resolution, field value) will only be applied to the selected issue types.

Filter by status

If you select specific statuses, all sub-tasks must be in any of the selected statuses. If subtasks with other statuses are found, the condition will fail.

The additional filters can be used to further restrict the state of the issues in the selected statuses.

If you leave this filter blank, e.g. if the status is irrelevant, you must check the additional option Allow unselected statuses. → Ignore status filter / issues in unselected statuses

If you select specific statuses and also check the additional option Allow unselected statuses, the additional criteria (issue type, resolution, field value) will only be applied to the issues in the selected statuses.

Filter by resolution

If you select specific resolutions, all sub-tasks must have any of the selected resolutions. If subtasks with other resolutions are found, the condition will fail.

The additional filters can be used to further restrict the state of the issues with the selected resolutions.

If you leave this filter blank, e.g. if the resolution is irrelevant, you must check the additional option Allow unselected statuses. → Ignore resolution filter / issues with unselected resolutions

If you select specific resolutions and also check the additional option Allow unselected resolutions, the additional criteria (issue type, resolution, field value) will only be applied to the issues with the selected 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

All sub-tasks must be assigned to a user. If unassigned sub-tasks are found, the condition will fail.

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

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

All sub-tasks must have a due date of equal to or later than the current issue's due date..

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

If you specify an expression and also check the additional option Allow unsatisfied condition on field values, the additional criteria (issue type, resolution, field value) will only be applied to the issues that match the expression.

Minimum number of sub-tasks

Specify the minimum number of the sub-tasks that need to satisfy the specified filter criteria. The default value is 0 to ensure the condition passes if the current issue does not have any sub-tasks.

If you set this number to 1, the condition will fail if the issue does not have any sub-tasks or if the existing sub-tasks don't match the specified filter criteria.

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
Ignore issue type filter / issues in unselected issue types

Check this option in the two cases:

  1. You have left the issue type filter blank: In this case you want to ignore the issue type filter and basically make sure that the other criteria you specify must be met in order for the condition to pass, regardless of the issue type. An equivalent would be to select all available issue types in the filter.
  2. You have selected specific issue types in the issue type filter:  In this case, sub-tasks which issue type is different to the ones selected in the filter, will be completely ignored by this condition. 
Ignore status filter / issues in unselected statuses

Check this option in the two cases:

  1. You have left the status filter blank: In this case you want to ignore the status filter and basically make sure that the other criteria you specify must be met in order for the condition to pass, regardless of the status. An equivalent would be to select all available statuses in the filter.
  2. You have selected specific statuses in the status filter:  In this case, sub-tasks in statuses is different to the ones selected in the filter, will be completely ignored by this condition. 
Ignore resolution filter / issues with unselected resolutions

Check this option in the two cases:

  1. You have left the resolution filter blank: In this case you want to ignore the resolution filter and basically make sure that the other criteria you specify must be met in order for the condition to pass, regardless of the resolution. An equivalent would be to select all available resolutions in the filter.
  2. You have selected specific resolutions in the resolution filter:  In this case, sub-tasks with resolutions different to the ones selected in the filter, will be completely ignored by this condition. 

Check this option in the two cases:

  1. You have left the field value blank: In this case you want to ignore the field value filter and basically make sure that the other criteria you specify must be met in order for the condition to pass, regardless of the field values. 
  2. You have specified field values in the field value filter:  In this case, sub-tasks with field values different to the ones selected in the filter, will be completely ignored by this condition. 


Use cases and examples

Title
No content found.

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