This post function can be used to copy a field value from multiple issues to the current issue.
By default, the linked issues' fields will be read. If sub-tasks should also be taken into account, the checkbox (see below) has to be checked.
Configuration
Add a field to configure and select a field value. The following options are available:
Copy field value from current issue
Choose the Field to copy from.
Set field value manually (parser expression)
Enter the Expression
And as an additional option, you can choose Write protection to not overwrite existing values.
Info
Only issues meeting the filter will be used to copy the field value from.
Filter project
Filter your project by choosing from one of the following options:
- Any project
- Current project
- Any but current project
Filter by issue link type
Only issues linked to current issue by selected issue link types will be read.
The following options are available:
| Option | Description |
|---|---|
is blocked by (Blocks) -inward | |
blocks (Blocks) -outward | |
is cloned by (Cloners) -inward | |
clones (Cloners) -outward | |
is duplicated by (Duplicate) -inward | |
duplicates (Duplicate) -outward | |
relates to (Relates) -inward | |
relates to (Relates) -outward |
Filter by issue type
The selected issue types will used to filter the linked issues and sub-tasks, but if you don't select any, it won't be applied any issue type filter. In that case, all issue types are allowed.
Filter by status
Only linked issues and sub-tasks with the specified statuses will be read. If no status is selected, all issue statuses are allowed.
Filter by field value
Enter a parser expression. The expression must return a true or false
You can try your expression by clicking the play button on the top right of the JQL expression box.
| Option | Description |
|---|---|
Read also sub-tasks fulfilling condition on issue type, status and project | This option only makes sense when the current issue itself is not a sub-task |
Read also sibling sub-tasks fulfilling condition on issue type, status, and project | Sibling sub-tasks are understood as sub-tasks with the same parent as the current issue. This option only makes sense when the current issue is itself a sub-task |
Read linked issues and sub-tasks recursively | Issues and sub-tasks transitively linked will also be read, provided they fulfill stated filtering conditions. Issues are read recursively without depth limit, but each selected issue is read-only once |
Read also current issue | Current issue will be included in the issue selection, i.e., current issue's field value will also be read |
| Update issue immediately | A specific entry will be created in issue history for this field writing |
The result of the logical expression must return a boolean value of either:
true→ the post function will be executedfalse→ the post function will not be executed
Using the conditional operator, even complex or multi-layered conditions can be constructed.
Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode
Choose which user* will be used to execute this post function. By default, it is set to the Current user.
Use cases and examples
| Title |
|---|
| No content found. |
If you still have questions, feel free to refer to our support team.
