| Info |
|---|
This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, see our JSU Server/Data Center documentation. |
...
On this page: | Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 6 |
|---|
| outline | false |
|---|
| style | default |
|---|
| type | list |
|---|
| printable | true |
|---|
|
|
Description
The Copy or Move Attachments post function will copy copies attachments from/to all related issues. You can define which issue should be a source and which is a destination. One or more attachments can be copied to the related issue(s). You can also use the post function to move attachments added on a transition screen.
See Workflow post functions to learn how to add a JSU post function to a Jira workflow.
Configuration
...
Precondition
| Include Page |
|---|
| Precondition UsagePreconditionsPrecondition Usage |
|---|
| Preconditions |
|---|
|
Issue Relation
| Include Page |
|---|
| Related Issuesissues |
|---|
| Related Issuesissues |
|---|
|
Perform As User
| Include Page |
|---|
| Perform As User |
|---|
| Perform As User |
|---|
|
Copy attachment from/to any related issue
You have different options for defining which issue/s will be treated as source/destination for attachments. Several of JSU's workflow modules provide the option to define the scope for some related issues.
For example, instead of copying attachments from one issue to the others, you might choose to copy them from all linked issues to the issue in transition (e.g. to group all attachments within one issue)
| Info |
|---|
Conditional copying attachmentsConditional copying attachment (controlled by custom field) is always only checked for issues in transition, regardless of whether the issue in transition is a source or destination. |
Related pages
...