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 18 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.  

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 issues to be analyzed.

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 issues to be analyzed.

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 issues to be analyzed.

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 value is 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

The following options can be used to refine the number of issues you want to analyze in this condition / validator.

Per default all filters are mandatory, filters are and concatenated and you cannot save your configuration unless you have specified values. The additional options allow you to override the default behavior.

CaseAdditional optionDescription
You have left a specific filter blankChecked (tick)

In order to evaluate whether the condition / validator passes, this filter will be skipped. An equivalent would be to select all options in a filter.

You have left a specific filter blankNot checked (error)Not possible. If you want to skip the filter you have to uncheck the corresponding additional option.
You have selected values in a filterChecked (tick)

In case you have selected values in a filter and check the corresponding additional option, the validation of the issues will ignore issues with unselected values when evaluating whether the condition / validator passes. 

By default, whenever a value was selected in a filter it will be combined with all other defined filter criteria and all sub-tasks must match the filter combination.

If you only want to analyze specific issue types (e.g. Test Cases), select Test case in the issue type filter and check the corresponding additional option. This way other sub-tasks (which are not cases) can exist and will not be considered in the validation.

You have selected values in a filterNot checked (error)In case the additional option is unchecked, you enforce that all sub-tasks which are analyzed must have the selected values.

Examples

The table below lists a few example configurations and their JQL equivalent.

ConfigurationJQL
  • Issue type: Sub-task
  • Status: Closed
  • Resolution: blank
  • Additional options: 
    • Skip resolution filter
type = Sub-task AND status = Closed and resolution IS EMPTY
  • Issue type: Sub-task
  • Status: Closed
  • Resolution: blank
  • Additional options: 
    • Skip issue type filter
    • Skip resolution filter
(type = Sub-task AND status = Closed and resolution IS EMPTY) OR type != Sub-task
  • Issue type: Sub-task
  • Status: Closed
  • Resolution: Done
  • Additional options: 
    • Skip issue type filter
    • Skip resolution filter
(status = Closed AND type = Sub-task AND and resolution = Done) OR type != Sub-task OR resolution != Closed


OptionDescription
Skip issue type filter / ignore issues in unselected issue types

xxx

Skip status filter / ignore issues in unselected statuses

xxx

Skip resolution filter / ignore issues with unselected resolutions
  1. xxx 

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.