Use cases

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

Whether you have a specific need to solve or want to explore the wider possibilities of JSU, our use cases will help get you started. We have included examples of our more common use cases for you with scenarios or step-by-step instructions. You can use JSU to create simple automation rules or build more intricate combinations to bring more powerful functionality to your Jira projects. Why not try some out in a test instance?

To follow the use cases below, you will need Jira administrator permissions and be working with company-managed projects. It is expected that you know how to edit and publish a draft workflow in Jira. If you aren’t familiar with editing workflows, see our Jira Workflow Fundamentals topics or visit Atlassian’s documentation for Jira Cloud Administrators. We recommend that you try out your rules in a test environment before publishing changes to live projects.

To help ensure that your JSU rules work the way your team expects, test your workflows in a test project with user permissions that represent the different roles within your team.

Use Case	Summary

Use Case	Summary
Add a comment to a linked issue in a service management project	Add a predefined comment to issues linked to a support ticket to inform the support team that the issue is done
Automatically Remove a Closed Epic From the Backlog	Let JSU keep your backlog clean for you
Calculate Values for an Epic	Use Jira to run a calculation rather than extracting data to another platform or performing the calculation manually
Close Parent Issue When All Subtasks are Done	Remove time-consuming tasks by automatically closing parent issues
Copy or Move Attachments	Automatically share attachments with team members
Copy or Set Value Fields on Linked Issue Creation	Pre-populate fields in linked issues
JQL Use Cases	Add flexibility and refinement to your workflows with JQL
Remove Assignee When an Issue Moves Back to To Do	Set the Assignee field to Unassigned when the issue moves back to TO DO
Streamline an Approval Process	Eliminate unnecessary downtime and friction from your approval processes
Testing and Fixing Bugs	Use multiple post functions to interconnect different workstreams
Update an Issue Only in Certain Conditions	An introduction to preconditions

Do you have another use case that you want to share with other JSU users? Let us know!