| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
...
This post function will copy attachments from/to all related issues. A user defines which issue should be a source and which is a destination. Any number of attachments can be copied to the related issue/-(s).
Configuration
...
Precondition
...
There are several ways in which preconditions can be evaluated in the context of a post function:
Ignore precondition (By default every precondition is ignored which means that the post function will always be performed)
True (Precondition must be true to execute a post function)
False (Precondition must be false to execute a post function)
...
Copy attachment from/to any related issue
You have several options , which 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 on some related issues.
For example, instead of copying attachments from one issue to another, you might choose to copy them from all linked issues to the issue in transition (e.g. to group all attachments within one issue)
...
Related issues will be found by one of the following Jira concepts:
...
| Note |
|---|
Conditional copying attachmentsConditional copying attachment (controlled by custom field) is always checked only for the issue in transition, regardless of whether the issue in transition is a source or destination. |
Source and destination
For example, the Copy Value From Other Field post function allows you to You can 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 written to the destination issue. Other workflow modules do not have source and destination; you just define the issue relation, which will apply to that workflow module.
For example, Create a Linked Issue will create a new issue, and then connect it through an issue relation to the issue in transition.
Controlled by custom field
Here you have With a checkbox custom field on the transition screen so that the , a user can control some of the functionality.
...
You can also choose 'Move Attachments added during Transition'. When a user adds some attachments on the transition screen of the source issue, it appears as if they added the attachments to all related issues.
Perform As User
...
...
Position of the post function
...
| Note |
|---|
If you use ‘Move Attachments added during Transition' it is important that the 'Copy / Move Attachments' post function is before the Jira’s 'Update change history for an issue and store the issue in the database' post function. In such case ‘Copy Move Attachments’ must be placed between ‘Update change history for an issue and store the issue in the database’ and 'Re-index an issue to keep indexes in sync with 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.