Less effort → less time → less lost money. That’s what every business desires, and that’s why automation is so popular. It really can make a difference when your workflow is stuck with manual, repetitive processes. Jira Automation isn’t some magical spell, it is not so simple to make it work. You’ll need some practice to create automation rules successfully. Let’s try to simplify this process a bit.
It looks like every second person in Atlassian Community asks something about automation. Though the configuration can be really tough, users understand they will win more after everything is done correctly.
Jira automation means the system can catch almost every change with your issues and performs the action based on it. For example, once the Jira issue status is changed, the system creates a branch and links it to the issue. The library of triggers, conditions and actions can cover even the most specific process in your company.
Jira Automation has some limitations you should be aware of and consider before building all the company’s processes there.
Our SaaSJet team has faced some of these items, so we’ve come up with an idea to lessen those limitations. That’s how the Business Process Manager (BPM) add-on came to life. It allows users to build the process based on Jira issues. So, the Process here is a Template of forms (Jira form) that will be added to automatically created issues.
You can organise form logic, approval (form approval, authorisation) settings and the order of how all these parts will be started. In other words, a user has to set the forms to submit, choose the project users will be able to see, assign it to users or/and groups. Then this Template (issue template) can be used as a Process instance an unlimited amount of times. It can perfectly work for Onboarding & Offboarding processes, Timelog discipline or vacation requests.
Business Process Manager’s Advantages:
All these advantages can perfectly empower Jira Automation and make your process more tailor-made. We recommend building the process in BPM and setting rules in Automation to start the process at the right time based on triggers from Jira.
A good example here is a product release. In Jira, it’s just a button; however, you can set the procedure that will assign the checklist to the release manager with core actions he should do.
This is the simplest example of how we organize the release process at SaaSJet.
The main message here is that BPM resolves the limits the Automation has.
Limitations of Automation
How BPM add-on helps
It has limits based on your subscription plan.
BPM doesn’t have any limitations. Using it with Automation you can decrease the amount of Rules you need as well as the number of execution of these Rules.
Cross-projects automation setup
BPM can work with any type of Project, create the Jira issues with forms there and run the authorisation.
All Templates have a Permission schema. The intuitive interface doesn’t require tech skills or consultation.
Jira setting communication
All Process Templates, Procedures and finally Process in one place. Team can work on it any time.
There is no perfect tool to save your efforts, time and money. Jira Automation is a really good choice for those who want to reduce time on repetitive tasks. Here is a formula for winning more while applying automation:
Jira Automation + Business Process Manager Add-on = Perfect match to work smarter, not harder.
Try out how BPM & Jira automation works together.
Karyna Tyrnavska _SaaSJetMarketplace Partner
Calling all collaborators and Confluence users! Our Appy Hours event on September 29th features 4 presenters demoing functionality to superpower Confluence. Don't miss learning about these apps i...