As a Jira admin, looking for ways to expand your Jira functionality, you may have stumbled across people using and referring to this thing called SIL. Contrary to what some may think, SIL is not the Grammy Award winning singer of "Kiss from a Rose" fame (though, like Batman it will definitely help save the world)! No, SIL stands for Simple Issue Language™ and is a very very simple scripting language for people without strong programming abilities who still want to customize Jira and automate the multitude of functionalities that Jira can offer with a few simple commands.
Using SIL, here are a just a few things you can customize on Jira:
SIL is intended to simplify work for users who do not want to deep dive to implementation details of Jira or users who do not know Java. Better yet, unlike writing in Groovy/ Java, SIL removes the need to account for dependencies, classes and packages before scripting to alter Jira. One of our users summed it up perfectly, "Using SIL I can just follow the workflow logic, I don't need to switch my mind to another subject. It helps to keep focused on business requirements and tasks rather than recall programming language."
SIL was designed to provide an easy, re-usable set of scripts which are flexible, easily configurable and do not need to be upgraded every time you upgrade Jira thus reducing your technical debt.
However, just because it's simple, doesn't mean you are losing functionality. SIL retains as much flexibility as possible exposing what we believe to be the basics of workflow customization, email handling, issue listeners, scheduled tasks, and so on.
Even better, SIL is not limited for use on Jira, the SIL language is actually independent from Jira. Below are a few of our apps which are powered by SIL:
Consider the following example: You want to resolve all open sub tasks for an issue that you've created in Jira.
Here is how you would code it using the Java/ Groovy script language (note: the top part is all the dependencies you need to know about and bring in before you even start writing the code!):
Here is the equivalent postfunction in SIL:
Short and to the point. SIL removes the need to write lines upon lines of code (who wants to be Bart Simpson on detention?) with a language that's easy to master, leaving you more time to tackle bigger problems.
Choosing SIL is a smart thing to do:
SIL lets you customize your Jira to really suit your individual needs, and lets you make these adjustments in a fraction of the time then you would spend using Groovy/ Java. If you're ready to dive in to more SIL use cases and instructions on how to get started with SIL, check out our SIL space on confluence or watch this short video which features more tips, tricks and templates on how to use SIL.
Michele Lim [cPrime]
Introduction Many users have difficulty in the initial phase of using Portfolio for Jira. They try to start quickly, in connection with which arise many questions and difficulties and as a result th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events