| Panel | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
This is the documentation of JSU for Jira Server. If you are using JSU on Jira Cloud, you can find the documentation here. |
| Table of Contents |
|---|
| Info |
|---|
The 'Copy / Move Attachments' feature is available from JSU 2.9.0 |
...
- Issue Link
You can define the link type to defined 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 related by an epic link, or it is part of an epic.
...
Instead of letting the user choose to copy/move the attachments, you can also configure to never/always copy them.
Tip: You might choose 'Move Attachments added during Transition'. The user then adds some attachments on the transition screen of the source issue. However since they are moved to all related issues, it feels as if he just added the attachments to all related issues.
...
| Info | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
If you use 'Move Attachments added during Transition' it is important that the 'Copy / Move Attachments' Post-Function is before JIRA Post-Function 'Update change history for an issue and store the issue in the database'!
|
...
When an identical attachment (same file name and same content) already exists in the destination issue, it will not be copied again. This is the case for both, existing and transition attachments.
Real life tips
Tip: You might setup a special transition screen to mainly copy those attachments to all linked issues. So it feels more like it would be the create screen of the new issue. In that case, you won't show those fields on the origin issue, but reset them again afterwards (just empty or back to the default value).
...