...
...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| Info | ||||||||||
This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, you can find the documentation here. | ||||||||||
| Info | ||||||||||
The 'Copy / Move Attachments' feature is available from JSU 2.8.0see our JSU Server/Data Center documentation. |
...
On this page:
|
Description
This post function will copy attachments from/to all related issues. A user defines You can define which issue should be a source and which is a destination. Any Any number of attachments can be copied to the related issue/-s.
Configuration
(s).
The Copy / Move Attachments post funtion is available from JSU 2.8.0
Configuration
...
Post function options
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
Issue Relation
| Include Page | ||||
|---|---|---|---|---|
|
Perform As User
| Include Page | ||||
|---|---|---|---|---|
|
Copy attachment from/to any related issue
You have several different options , that for defining define which issue/s will be treated as source/destination for attachments. 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 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)
| Warningnote | |
|---|---|
| title | Conditional copying attachmentsConditional copying attachment (controlled by custom field) is checked always only checked for issue issues in transition.Independently if , regardless of whether the issue in transition is a source or destination. |
Asynchronous Execution
| Include Page | ||||
|---|---|---|---|---|
|
Example
See the Use Case CopyCopy/Move attachmentsuse case for a nice an example , of how several some of our customers use it.
...
Supported Field Types
| Include Page | ||||
|---|---|---|---|---|
|