Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
This condition on a set of issues given a list of its issue keys. The following aspects are evaluated: issue type, issue status, project membership, and the number of issues.can hide a transition based on the state and the number of issues stored in an issue field (e.g. a custom text field). You can specify multiple filter criteria that will be "and concatenated". By default, all identified issues must match the combination of all criteria. |
Configuration
UI Expand | |||||
---|---|---|---|---|---|
| |||||
Select a specific field, e.g. Summary, Description, Issue key...etcthe text field containing the issues.
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
If you select specific issue types, all issues must be of any of the selected issue types. If issues with other issue types are found, the condition will fail. The additional filters can be used to further restrict the issues to be analyzed.
Only issues with the selected issue types are allowed. Leave empty to allow all issue types. The following options are available: |
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
If you select specific statuses, all issues must be in any of the selected statuses. If issues with other statuses are found, the condition will fail. The additional filters can be used to further restrict the issues to be analyzed.
Only issues with the selected statuses are allowed. Leave empty to allow all statuses. The following options are available: |
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Only issues with the selected project are allowed, the Optionally specify specific projects, the linked issues must or must not belong to. The following options are available:
|
UI Expand | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
Optionally limit the issues to be counted or analyzed by their field values. To achieve this you must enter an expression in Logical mode. The expression must return
|
UI Expand | ||
---|---|---|
| ||
Choose Specify the minimum number of issues required to satisfy selected filtering conditions (issue type, status, project and field values)that need to satisfy the specified filter criteria. The default value is 1 to ensure the condition fails if the field does not contain issue keys. |
UI Expand | |||||
---|---|---|---|---|---|
| |||||
Choose Specify the maximum number of issues allowed to satisfy selected filtering conditions (issue type, status, project and field values)that need to satisfy the specified filter criteria. The default value is 9999.
|
UI Expand | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
The following options can be used to refine the number of issues you want to analyze in this condition. Per default all filters are mandatory, filters are "and concatenated" and you cannot save your configuration unless you have specified values. Any sub-task being analyzed by the condition must match all criteria.
The additional options allow you to override the default behavior.
ExamplesThe table below lists a few example configurations and their JQL equivalent.
|
UI Text Box | ||
---|---|---|
| ||
If you want to use this functionality in a validator instead, have a look at the following condition: Validation on a list of issue keys Choose from one of the following options (multi-choice is possible): | ||
Option | Description | |
Ignore issues in non-selected issue types | Issues in non-selected issue types will be ignored, i.e., they will be allowed regardless of their number. | |
Ignore issues in non-selected statuses | Issues in non-selected statuses will be ignored, i.e., they will be allowed regardless of their number. | Ignore issues not meeting filter by field values | Issues not satisfying filter by field values will be ignored, i.e., they will be allowed regardless of their number.
Use cases and examples
Page properties report | ||||||
---|---|---|---|---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Page properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|