...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, you can find the documentation here. |
| Info |
|---|
The 'Copy / Move Attachments' feature is available from JSU 2.8.0 |
Description
This post function will copy attachments from/to all related issues.
A user defines which issue should be a source and which a destination.
Any number of attachments can be copied to the related issue/-s.
Configuration
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
We use the Update any Issue Field post function like this in the 'Start Progress' transition of our Story issue types. If the Story is part of an Epic, the Epic Status will be set to 'In Progress'.
In the past users forgot to change the Epic Status in time and it was left behind as 'To Do'. Using JSU this does no more happen.
Issue Relation
| Include Page | ||||
|---|---|---|---|---|
|
Perform As User
| Include Page | ||||
|---|---|---|---|---|
|
Copy attachment from/to all issues related as
You have several different options, which defines which issue/s will be treated as source/destination for attachments.
Several of JSU's workflow modules provide the option the 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 issues)
Types of issue relations
Related issue will be found by one of the following JIRA concepts:
- Issue Link
You can define the link type to defined which issues exactly will be affected by the operation. - 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.
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 that issue, which triggered a workflow condition / validator / post function to be executed.
| Warning | ||
|---|---|---|
| ||
Conditional copying attachment (controlled by custom field) is checked always only for issue in transition. Independently if issue in transition is a source or destination. |
Source and destination
For example the Copy Value From Other Field Post-Function allows you to 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 be written to the destination issue.
Other workflow modules do not have source and destination. So you just define the issue relation, which will apply for that workflow module.
For example Create a Linked Issue will just create a new issue and then connect it with some Issue Relation to the issue in transition.
Asynchronous Execution
| Include Page | ||||
|---|---|---|---|---|
|
Example
<tbd>
Supported Field Types
| Include Page | ||||
|---|---|---|---|---|
|