Page History

This validator depends on issue type, status, resolution, and number of sub-tasks.

Only sub-tasks with the selected issue types are allowed. Leave empty to allow all issue types.

Only sub-tasks with the selected statuses are allowed. Leave empty to allow all statuses.

Example of possible statuses:

• Open
• To Do
• In progress
• Done
• Approved

Only sub-tasks with the selected resolutions are allowed. Leave empty to allow all resolutions.

Example of possible resolutions:

• Unresolved (resolution is empty)
• Done
• Duplicate

Only sub-tasks matching the field value condition provided will be allowed. Leave empty for no filtering.

The minimum number of sub-tasks required to satisfy selected filtering conditions (issue type, status, resolution, and field values).

The maximum number of sub-tasks allowed to satisfy selected filtering conditions (issue type, status, resolution, and field values).

• Allow unselected issue types - Sub-tasks in unselected issue types will be ignored, i.e., they will be allowed regardless of their status, resolution, field values, and number. Nevertheless, if none of the issue types are selected, checking this option will make the condition behave as if you had selected every issue type.
• Allow unselected statuses - Sub-tasks in unselected statuses will be ignored, i.e., they will be allowed regardless of their resolution, field values, and number. Nevertheless, if none of the statuses are selected, checking this option will make the condition behave as if you had selected every status.
• Allow unselected resolutions - Sub-tasks in unselected resolutions will be ignored, i.e., they will be allowed regardless of their field values and number. Nevertheless, if none of the resolutions are selected, checking this option will make the condition behave as if you had selected every resolution.
• Allow unsatisfied condition on field values - Sub-tasks not satisfying filter by field values will be ignored, i.e., they will be allowed regardless of their number.

Choose from one of the following options (multi-choice is possible):

• Skip validation for JWT post functions - If the transition is triggered by a JWT post function, the validation will be skipped.
• Skip validation for bulk operations - If the transition is triggered by a bulk operation, the validation will be skipped.
• Skip validation for clone operations - If the create transition is triggered by a clone operation, the validation will be skipped.
• Skip validation for mail handlers - If the create transition is triggered by a mail handler, the validation will be skipped.

Add an optional error message to show when validation fails.