Several of JSU's workflow modules provide the option to define the scope of the module on some related issues.
For example, instead of copying a field within an issue during a post function, you might choose to copy it to a sub-tasksubtask.
Types of Issue Relations
...
The related issue will be found by one of the following Jira concepts:
Issue Link
You can define the link type to define which issues exactly will be affected by the operation.
Since JSU 2.2.0, we introduced the value ANY. The operation will be performed on any linked issues.Parent / Sub-Task
The related issue is either parent or sub-task of each other.Epic / Issue in Epic
This is only applicable if you have Jira Software installed.
The other issue is either the epic is related by an epic link, or it is part of an epic.JQL
A JQL query will be executed to find the issues, which will be affected by the post function. You can use some placeholders in the JQL query, which will be replaced with the current field values of the issue in transition.
For writing the JQL query please follow the instructions on JQL Reference.
See our JQL Use Cases for some examples.
...
For example, the Copy Value From Other Field Post Functionpost function allows you to define the issue in transition as the source or destination of the copy operations, while you define the other end with an issue relation.
The field value will then be read from the source issue and be written to the destination issue.
...
Copy Value From Other Field Post Functionpost function: there should be only one source issue. Otherwise, it is not clear from which the value will be read. (The current implementation will just randomly pick one of them and ignore the rest.)
If you use Create a Linked Issue to create a new sub-task, you must also configure this post function to create the new issue as an issue type of a sub-task and make sure the target project is the same as the one of the issue in transition.
...