| Table of Contents |
|---|
...
If you use 'Move Attachment' (see bellow) you must position the post function before 'Update change history for an issue and store the issue in the database.'
You can add this post function several times in one transition and it will duplicate attachments.
This post function can be also used in a combination with preconditions.
...
| 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'!
|
...
| Warning |
|---|
Due to a Bug in Jira JRASERVER-65939, 'Copy or Move Attachments' functionality, which are added through a Transition Screen, does not work in Jira 7.5.x & 7.6.0. If you require this functionality, please upgrade to minimum Jira Version 7.6.1! |
Already existing attachments are not copied again
When identical attachment already exists for destination issue it will not be copied again. A dedicated algorithm compares file names, sizes, byte codes to decide if source attachment should not be copied again to a destination issue. The algorithm works both for 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).
...