Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

JSU for Jira Cloud

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


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 Copy/Move attachments post function and it will copy the document from the parent issue to your team’s sub-tasks.

How to configure this workflow

  1. In your project’s left side menu in Jira, select Project Settings and then select Workflows

  2. Select the Edit button to open a draft of the workflow. 

  3. Click Text view, then select the “in progress” transition. 

  4. Select the Post Functions tab, then click Add Post Function.

  5. Select the Copy/Move attachments (JSU) post function then click Add at the bottom of the page.

  6. Configure the post function:

    1. Choose the Parent/Sub-task 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 sub-tasks. 

    2. 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 sub-tasks. 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.

    3. 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. 

  7. Click Add.

  8. Publish your workflow.

Test your new post function

  1. 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 to enable the rule you have configured in your post function.

  2. Move your parent issue to "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.

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 sample of JSU in action. Subscribe to our YouTube channel and access more JSU use cases.
See our 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!


  • No labels