SIL® vs. Groovy


We created our own language layer, Simple Issue Language® or SIL®, to simplify the common complexities of writing Groovy into simple one line routines. This way, you can simplify your custom solutions to be quick to implement and easy to scale without going rogue and jeopardizing your instance.


Our developers handle all of these dependencies so you and your Jira Admins don’t have to. Here’s what you can look forward to with SIL®:

  • We maintain all the dependencies and the issues so you don’t have to worry about broken scripts and a backlog of technical debt.
  • If you wrote a script in an older version, it will work in the newer version and 10 versions from now without having to touch it.
  • You can leverage our scripting across multiple instances and take advantage of a federated aspect of SIL® communicating across instances.
  • Most of our solutions are in code ready templates that allow you to copy and paste them to be used (See our ready-made tutorials, templates, and routines section).

While we want you to get to SIL®, we know it may take you a few groovy scripts to get here. We are here for you with open arms, willing to help you. We look forward to getting you on the right path towards a true enterprise script framework.

Still don’t believe us? Let’s look at a simple example! The learning curve is easy.




Routines from SIL® are one-liner, pre-built, code-ready scripts that our users commonly ask for. If you are looking for an easy solution visit out routines section and feel free to copy and paste away into your SIL® Manager.

Here’s a 1 line code sample of a SIL® Routine:

0 Imports.
1 line of code.
2 words.


For groovy solutions, you are essentially opening a window into the Jira API and it requires you to understand all the intricacies of Groovy and Jira internals to cobble together your solution. Sadly, these tend to break very frequently and it becomes a struggle to maintain this at scale let alone in one project.

*note: truncated to fit on the page.

Here’s a 26 line code sample of a Scriptrunner groovy script that creates a scripted custom field.

      • This code requires 6 imported files.
      • Users who will write, interact, and maintain this code in the future will have to understand all the class files required to make this script.
      • We commonly see hundreds of scripts deployed across Dev, Test, and Production so this just magnified that you have a maintenance problem here.

Read more here >

No need to wait any longer. Get started today!