This is the documentation for JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, see the Server/Data Center documentation.
Save your team’s time and effort by automatically copying attachments to all of an issue’s subtasks
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 subtasks 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. All you need to do is configure the JSU Copy/Move attachments post function and it will copy the document from the parent issue to your team’s subtasks.
Create a draft of your project workflow. If you're unsure how to get to this page, follow the onboarding steps in Edit a Jira Workflow. You can then view your workflow in Text or Diagram mode. The steps in this use case represent Text mode. If you haven't already, switch the workflow viewer to Text mode.
Select the in progresstransition.
Select the Post Functions tab, then click Add Post Function.
Select the Copy/Move attachments (JSU) post function then click Add at the bottom of the page.
Configure the post function:
Choose the Parent/Subtask issue relation since you want the post function to perform when the parent issue is transitioned and for the attachments to be copied to the subtasks.
Select the Always copy attachments option from the drop-down menu so that all the attachments you will add during the transition on the transition screen are copied through to the subtasks. You have the option to select a field of your parent issue to have a value, for the attachments to be copied to the sub-tasks. If you use this option, 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 as well.
Publish your workflow.
Test your new post function
Go to your issue and create subtasks for your team members. At this stage, you will need to assign a transition screen to the in progress transition to enable the rule you have configured in your post function.
Move your parent issue to in progress then upload the creative document on the transition screen you created. Refresh the screen and see what you have achieved with JSU! Open your subtasks and check your attachments. The document is there, and the whole team can start working without going back and forth on the parent issue.
Attention! Make sure you edit the project's attachment permissions to be able to copy/move attachments.
Watch this video to see all of this in action*:
This was only a sample of JSU in action. Subscribe to our YouTube channel and access more JSU use cases. *The video is created on the Jira Server environment.