Good Jira automation just stays out of the way and helps you get things done without thinking about it. But building good automation isn’t always easy, even when you go beyond Atlassian’s built-in capabilities and use add-ons.
Jamie Echlin, Adaptavist Staff engineer and creator of ScriptRunner, will talk about those situations where building automation in Jira can backfire. Running JQL functions in script fields, slow workflow condition functions, adding javascript to the announcement banner, inline scripts and endless loops are among the most common pitfalls for a Jira admin. Jamie will show you how to avoid them and will share some handy advice for building powerful automation in a responsible and scalable way.
Tips on what can go wrong and what can go right when building complex workflows.
Adaptavist
Staff Engineer & ScriptRunner Creator
Adaptavist
Senior Product Marketing Manager
Jamie Echlin has been working with dev tools since the mid-1990s, primarily in investment banks. Having worked with ClearCase, ClearQuest, Perforce and more, he graduated to the Git and the Atlassian stack.
He began developing ScriptRunner for JIRA in 2007, mainly just to make his own life easier. ScriptRunner has now been installed over 16,000 times and is available for JIRA, Confluence and Bitbucket.
Hugely active in the Atlassian Ecosystem, he helps users, teams and organisations with their dev tools and coding challenges. He joined the Adaptavist team in 2014 and now leads the product’s development team.
Owning a portfolio of flagship Adaptavist apps, my team's job is to bring clarity, structure, and simplicity to the way our complex products are represented in the world of Atlassian software.
Toronto ACE Leader
Atlassian Event Leader
TD
Atlassian User Group Leader
Banking and Financial
Atlassian Community Leader
Tatari
Toronto ACE Leader
