| 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. |
...
You have several options which define which issue/s will be treated as a source/ or destination for attachments. Related issues are evaluated by one of the following Jira concepts:
Issue Link: You can define the link type to define which issues exactly will be affected by the operation. From JSU 2.2.0, we introduced the value ANY. The operation will be performed on any linked issues.
Parent / Subtask:The related issue is either parent or subtask 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.
JQL: A JQL query will be executed to retrieve the issues. You can use placeholders in the JQL query which will be replaced with the current field values of the issue in transition. For tips on writing the JQL query, see JQL Reference.
Issue in transition
We use the term 'Issue in Transition' when we refer to the issue for which a workflow condition is checked, for which a workflow validator is examined, or for which a workflow post function is performed.
Or in other words, the issue which triggered a workflow condition/validator/post function to be executed.
| Note |
|---|
Conditional copying attachments Conditional 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
You can define the issue in transition as the source or destination of the copy operations. Other workflow modules do not have source and destination; you just define the issue relation, which will apply to that workflow module.
...
| 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’. |
...