Introducing AutoBlocks for Jira
The wait is over! We are proud to bring you our much anticipated new app; AutoBlocks for Jira Beta.
What is AutoBlocks?
AutoBlocks for Jira empowers Jira users and admins of all roles and technical acumen to standardise workflow best practices, create automations, and customise Jira with a simple, easy to use workspace.
Based on the Google Blockly Framework, AutoBlocks is a virtual whiteboard where users can customise Jira projects to meet the needs of their team with easy, drag-and-drop technology.
AutoBlocks’ drag-and-drop interface makes it easy to build automations visually.
Over the past year we have been working hard to offer a solution that gives users the power to automate using simple building blocks. Users can also distribute access to project owners to carry out their own automations in their Jira environment.
AutoBlocks will be available to admins, but they can grant access to any Jira user to use the platform to create their own automation workflow, their creativity limited only at the discretion of the Jira Admin.
An example of an AutoBlocks workspace. This white canvas is where you connect Blocks together to build automations.
How is AutoBlocks different to ScriptRunner for Jira?
ScriptRunner is the premier platform for automating, customising, and integrating the Atlassian stack. Using the scripting language Groovy, you can dive deep into Atlassian's platform at the code level. Over the past 10 years, Atlassian admins have used ScriptRunner to transform apps like Jira from a one-size-fits-all, complex platform, to a completely customised and branded DevOps powerhouse.
There are a few things to note:
- ScriptRunner is a deeply technical product that requires at least some coding knowledge;
- Only admins have the ability to use the product and provide benefit;
- Making complex changes to the entire development platform can be daunting for new users.
That's why we've built AutoBlocks - to democratise the power of automation and enable all users to mould Atlassian to their team's needs. Technically savvy users can still solve unique problems by scripting and empower their entire team to take advantage of these scripts using ScriptRunner.
But it’s a Beta, how does that work?
We are launching the Beta version to gain feedback and harness AutoBlocks to adapt to your needs. Out-of-the-box you can get on board with our step-by-step getting started guide that takes you through the basics of building your own workspace.
We are really excited to see how you get on with AutoBlocks. Let us know your thoughts and give us feedback through our support portal, even the smallest comments will help us improve your experience with AutoBlocks, so here’s your chance!
What lies ahead...
You don't need ScriptRunner to use AutoBlocks and vice versa. However, soon you will be able to integrate ScriptRunner and AutoBlocks in order to build more complex use cases for your workspaces.
For example, a Dev Lead might write a custom script (using ScriptRunner) that requires certain fields in Jira to be filled out before the ticket can be submitted. You can then add that script to your "Block" to create the same requirements for Jira projects as part of your workspace.
With the power of the Adaptavist Library, ScriptRunner, and AutoBlocks, you will have the ultimate automation bundle giving your team time back to focus on more challenging projects.