...
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.
| Tip |
|---|
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 | ||||
|---|---|---|---|---|---|
Add a predefined comment to tasks that are moved to a review status, to let the reviewers know it is ready for their review or approval | |||||
Let JSU keep your backlog clean for you | |||||
Use Jira to run a calculation rather than extracting data to another platform or performing the calculation manually | |||||
Remove time-consuming tasks by automatically closing parent issues | |||||
Automatically share attachments with team members | |||||
Pre-populate fields in linked issues | |||||
Add flexibility and refinement to your workflows with JQL | |||||
Set the Assignee field to Unassigned when the issue moves back to
| |||||
Eliminate unnecessary downtime and friction from your approval processes | |||||
Use multiple post functions to interconnect different workstreams | |||||
An introduction to preconditions |
...