Copy or Move attachments

JSU for Jira Cloud

This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, you can find the documentation here.

Imagine you are a Manager and your team was assigned a creative project. You have prepared a Creative Document containing details of the project and have uploaded this in a Jira issue. 

You have also created sub-tasks for each team member to work on. To ensure that all team members are aware of the details of the project, you would like to attach this Creative Document in all sub-tasks. 

JSU will save you time and effort from having to manually upload the document in each sub-task. All you need to do is configure the JSU post-function “Copy/Move attachments” and it will copy the document from the parent issue to your team’s sub-tasks.

Check out the "How to" video further below to configure your automation.

How to configure this workflow

  1. On the left side menu, go to project settings and choose the option Workflows. Then on the right hand side, click the edit button to edit your workflow. In this case, we will configure the post-function on the “in progress” transition. Move to the post-functions tab, click to add post-function and then select the "Copy/Move attachments" post-function from the menu

  2. Choose the Parent/Sub-task relation since you want the post-function to perform when the parent issue is transitioned and for the attachments to be copied on the sub-tasks. Select the "always copy attachments" option from the drop-down menu of the configuration to have all the attachments you will add during the transition on the transition screen copied through to the sub-tasks.In this drop-down, you have the option to select a field of your parent issue to have a value, in order for the attachments to be copied to the sub-tasks. By configuring this, the attachments added on the transition screen will only be copied to the sub-tasks if that field has a value. Follow the same steps if you want the attachments that existed in your parent issue before the transition started to be copied through too. At the end of the page click the add button to add your post-function. Do not forget to publish your workflow.
  3. Now, go to your issue and create sub-tasks for your team members. At this stage, you will need to assign a transition screen to the "in progress" transition in order to enable the rule you have configured in your post-function "copy/Move attachments added during transition". Configuring screens is a functionality offered by Jira out of the box and here is a quick way of doing it for this case.
  4. Turn your parent issue in progress and upload the creative document on the transition screen you created. Refresh and see what you have achieved with JSU! Open your sub-tasks and check your attachments. The document is there and now the whole team can start working without going back and forth to the parent issue.
  5. Attention! Make sure you edit the project's attachment permissions to be able to copy/move attachments.

How to video

Watch this video to see all of this in action*:

This was only a bit of JSU in action. Subscribe to our YouTube channel and Access more JSU use cases.
See also the app documentation for some more examples and configuration screenshots.

*The video is created on the Jira Server environment. 

Need more Information or help? Get in touch!