Page History
Page properties | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
The Issue Selector selector needs an issue (context) as a starting point. Therefore it can only be used with the following issue-related event trigger types: |
Issue
Selector configurationselector configuration
Below you will find a detailed description of each parameter needed to configure the condition.
Target issue
Target Issue(s)
Select the issues that should be
grabbedcollected by the selector. Based on the selection, additional filters can be set for limiting the result.
It can be chosen from one of the following options:- Parent Issue
- Sub-tasks
- Sibling Sub-tasks
- Linked Issue
- Linked Epic
- Issues under Epic/ Stories
- Sibling issues under Epic/ Stories
- Issue List Expression
Screenshot
UI Expand | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
|
Run as
Use Cases and example
Page properties report | ||
---|---|---|
|
Usage Examples
The Selector has been used in the following examples:
- Keep priority of parents and sub-tasks in sync
- Transition sub-tasks when parent issue is rejected
- Update summed up value in parent issue on field change in sub-tasks
Usage Examples
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|