JSU for every team
JSU is the top-selling Jira workflow automation app for large companies including Boeing, Facebook, and Tesla, among many others.
It’s voted Staff Pick amongst the thousands of apps and integrations available to customize Atlassian products to work for every team’s unique needs. Whether you are in HR, IT, R&D or any other team, there is a JSU feature that would benefit you.
Here are three of the many use cases any team could perform on Jira with the help of JSU.
They trust JSU
For IT teams
Do your Epics still stay on the Backlog of your Jira agile board after closing them? We know why! Besides the workflow status, Epics have an additional field called Epic status, only accessible on the Backlog screen. Only Epics with the field Epic status marked as “Done” get removed from the Backlog.
This beecom How to video teaches you how to make Backlog status follow Epic status with JSU.
Go to your project settings and click to edit your workflow. You can choose the transition you want to perform your post function. In this case we choose the “Done” transition.
Go to the post function tab and click to add post function and then choose the “Update any issue field” post function from JSU.
Finally click add.
Because we want this post function to perform only for Epics, we will need to configure a precondition.
Therefore, we set the precondition to be true at the beginning of the post function configuration. In this transition you want to have your Epic status updated to “done”.
Fill out the fields and click add.
Now it’s time to create your precondition to prevent errors when the workflow is used to non-Epic issues.
Click to add post function and choose the “Value field” precondition. Configure your precondition by choosing Issue type to be equal to Epic and make sure the comparison type is “String”.
You can now add your precondition. Don’t forget to publish your workflow.
Now check what you have achieved with JSU. Your Epic is currently visible on the Backlog. Turn your Epic to “Done” and go back to your Backlog.
Your Epic doesn’t show up any more!
„The JSU Suite extends the functions for workflows perfectly and thus also enables the mapping of complex workflows. As an Atlassian Solution Partner we use JSU for our own work and are happy to recommend it to others.“
Thomas Ascherl, Atlassian Marketplace
For Finance teams
Do you often set up issues that need approval to move to production? Do you need budget approval from your manager only for large budgets but not for smaller ones? In every organization, a budget approval process is required. Trigger budget approval efficiently and in accordance with your company’s policies and rules with JSU.
With JSU Automation Suite for Jira Workflows you can configure, that the workflow will transition automatically to the correct status.
Add the JSU Post Function Follow Up Transition in the „Submit Budget“ Transition to follow up next transition.
The post function will evaluate the workflow conditions of all the next transitions on the target status of the current transition.
If exactly one condition is valid, that transition will be triggered as a „follow up“ transition.
Set up two different Value Field Conditions for the different transitions „To be approved“ and „Approve“. You can choose the amount of budget above which your budget needs approval. In this case we put 1’000:
If Budget > 1’000 on the „To be approved“ transition, then the status turns to „TO BE APPROVED“
If Budget <= 1’000 on the „Approve“ transition, then the status turns to „APPROVED“
We have carefully set these conditions, that always exactly one condition is valid. Like this, the Follow Up Transition will always trigger one of these two transitions. The workflow will never be stuck at the Decision status.
Make sure you add the „budget“ field on your project screen before you move on with your issue creation.
Create an issue in your project and set you budget to 2’000. Start progress and check the status. JSU has automated the DECISION with the follow up transition and moved your issue to „TO BE APPROVED“ based on the conditions you set up before.
You can do the same by setting your budget to 800. Start progress and check the status. The automation turned the issue status to „APPROVED“
„We manage a lot of different Jira instances and have found that this is a required plugin for all of our Jira instances. The ability to configure workflows with the built in conditions and validators from JSU are used on almost all our workflows.“
Mark Lang, Atlassian Marketplace
For HR teams
Have you ever wished value fields of an origin issue can be copied automatically to its linked issues? Your wish is our command!
Let’s say you are a Hiring Manager and you are onboarding a new Marketing Assistant.
Your tasks to complete the onboarding would then include
- Create new contract
- Order new computer
First, you create your origin issue which you’ll call Hiring a Marketing Assistant. Instead of manually creating linked issues and copying field values, JSU’s New Set of Operations can help automate these tasks. These new Operations can do three things:
- Copy a field value from the origin issue to a new linked issue
- Copy the value from one field to another field within the origin issue, and
- Set value of a field in a new linked issue
Go to your project settings and choose the Workflows option from the left navigation. Then edit your workflow. We will perform our automation on the „in progress“ transition, so when the task turns to in progress, 2 sub-tasks will automatically be created! Choose the „in progress“ transition and switch to the post functions tab to add a post function
Select the „Create linked issue“ post function by JSU and click the add button below. In this use case, you do not need any preconditions, so you can ignore this part. You want your automation to perform inside the same project. And you want your new issue to be related via Sub-Task. You can choose whatever issue type you want but in this case, choose Sub-Task.
Time for a little magic now! You can configure the value of different fields by clicking on „Add configuration“. You can copy a field value from the origin issue to the new issue or within the origin issue. You can also set a field value to a field in the new issue. In this case, the origin issue is our task and the new issue is the sub-task.
First, you can copy a field from the origin to the new issue. Let’s copy the assignee of the task to the assignee of the sub-task. Then, you can copy a value from a field of the origin issue to another field of the origin issue. We’ll try it by copying the summary to the description prepending it with a dash. Configure the last operation by setting a value for the summary of the new issue. We’ll set it to „Create contract“.
Finish by adding your post function.
Follow the same process to have one more sub-task created for ordering a PC. Add the create linked issue post function and configure the value of the fields you prefer. Set the summary of your new issue to „order PC“ add your post function and publish your workflow.
Go to your project and create a task for hiring a Marketing Assistant. Edit the assignee and the description of your task and put it in progress.
The JSU post function automatically created 2 subtasks for you! The description of your task is updated because of the „copy within origin“ functionality. Your new sub-tasks have been assigned to the assignee of the task due to the „copy to new“ functionality and their summary is set as configured by the „set“ functionality. That’s it! JSU automated the work for you!
„A plugin you cannot live without. It offers some really essential tools for JIRA Admins to take workflow to the next level. The provided support is relevant, helpful & fast.. the kind you hope for, but rarely get.“
Ben De Pauw, Atlassian Marketplace