The Copy attachments to related issuespost function allows you to copy all attachments to sub-task, parent, or linked issues when a workflow transition is executed.
Select the relation type in the Perform action on field to decide if the attachments will be copied to sub-task, parent, or linked issues
If Parent or Sub-tasks was selected, set the Applies to field to decide if the attachments will be copied to issues with any or selected issue type. If Selected was set, choose the issue types in case of which the attachments will be copied in the Issue types field
If Linked was selected, set the Applies to field to decide if the attachments will be copied to issues link with any or selected issue link. If Selected was set, define the details of the issue link used to link issues to which the attachments will be copied:
Set the type of link in the Link type field
Set the direction of link in the Link direction field
Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)
If you have selected Current user option, the post function will be executed by the user making the workflow transition
If you have selected Another user option, provide a user in the User field, so that the post function will be executed by this user
Activate the JQL condition option and define the JQL query that has to be met by the issue in order to execute the post function (e.g. “type = Bug and Priority = Blocker”)
Activate the Executor condition option if you want the post function to be executed only if the user is or isn’t in a certain Jira user group or project role
Select if The executor has to be or can’t be a member of a certain Jira user group or project role
Select a Jira user group in the Group field if Group was set in the member of a field
Select a project role in the Project role field if Project role was set in the member of a field
The user set as Action executor in point 2 needs to have the Browse Projects and Create Attachments permissions in the project of the related issue in order to execute the post function.
Marketing task with multiple sub-task issues is approved and the attached documents are copied to its descendants