Static Type Checking

Static type checking (STC) provides information about whether your script is correctly written.

Groovy is a dynamic language, which means that method and property names are looked up when your code is run, not when it’s compiled (like Java).

Let’s look at the following simple, but complete, script:


We call the method bar() on the object foo. This script compiles without errors, but you get a MissingPropertyExceptionwhen you run the script because foo hasn’t been defined. This behaviour is useful because there are circumstances that could make this code execute successfully, like an object called foo or a closure getFoo() being passed to the script’s binding.

Although Groovy is a dynamic language, we can compile scripts in a manner that checks method and property references at compilation. The STC feature shows you problems in your scripts when you are writing them, as opposed to when they execute.

When your scripts are executed, they are always compiled dynamically. When they are compiled for the STC, the resulting generated bytecode is thrown away.


There are limitations to the type checker. It is possible to write code that shows errors, but it is valid and executes fine. Some of these situations are:

  • Using certain builders

  • Using closures where the parameter types can’t be inferred

However, if you write code like this, you probably use an IDE, which does not work with the STC.

Additionally, your code could have runtime errors that won’t be found until the code executes.


The code for a condition to check that the remaining estimate on the issue was zero might look like the following:

The STC shows that we are trying to set the estimate, rather than retrieve it. We should have used the equality operator:

Note the green dot, which tells us that the code is syntactically correct after checking the methods and properties.


The STC also shows methods and properties that are deprecated. These are parts of the API that Atlassian would prefer you not to use.

In the following image, there is one deprecated method:
type checked condition depr 2

It is advisable to change your code to the suggested alternative because Atlassian usually removes deprecated code on major version releases. If you switch to the non-deprecated code, there is a better chance of your script continuing to work on your next upgrade.

A fixed version of the above script might look like:
type checked condition depr fixed 1



To write classes, give information about the field types to the STC.

If you do not, you’ll receive the following STC errors:

Instead, declare your field types like this instead:

import com.atlassian.sal.api.component.ComponentLocator import com.atlassian.applinks.api.ApplicationLinkService class Foo { ApplicationLinkService applicationLinkService = ComponentLocator.getComponent(ApplicationLinkService) void doSomething() { applicationLinkService.getApplicationLinks() } }


When writing closures, you may need to provide additional type information.

For example:

import com.atlassian.sal.api.component.ComponentLocator import com.atlassian.applinks.api.ApplicationLinkService def applicationLinkService = ComponentLocator.getComponent(ApplicationLinkService) applicationLinkService.getApplicationLinks().findAll { == "Confluence" }

It is inferred from the context that the type of it is an ApplicationLink object.

While this code will execute without issues, the STC produces an error: No such property: name for class: java.lang.Object.

Using the following code, you can fix this error by explicitly informing the STC that the type of it is an ApplicatonLink object.

import com.atlassian.sal.api.component.ComponentLocator import com.atlassian.applinks.api.ApplicationLinkService import com.atlassian.applinks.api.ApplicationLink def applicationLinkService = ComponentLocator.getComponent(ApplicationLinkService) applicationLinkService.getApplicationLinks().findAll { ApplicationLink it -> == "Confluence" }

Either version of the code is fine. If you want to ignore the STC, you can. The version of the bytecode that is actually executed is always compiled in "dynamic" mode.

If you wanted to take the closure in the previous example and reuse it, you should write code like this:

import com.atlassian.sal.api.component.ComponentLocator import com.atlassian.applinks.api.ApplicationLinkService import com.atlassian.applinks.api.ApplicationLink def applicationLinkService = ComponentLocator.getComponent(ApplicationLinkService) def findApplicationByName = { ApplicationLink it -> == "Confluence" } applicationLinkService.getApplicationLinks().findAll(findApplicationByName)

Type Information

Certain parts of Atlassian’s API are not strongly typed.

For example, the methods for getting and setting custom field values are defined to receive and return a java.lang.Object. The type checker only has access to this information, and it is not aware of the types of your custom fields.​NOTE: A special case is when using cfValues['My Field'], where a special effort is made to attempt to introspect the type of field named My Field.

The following script, which sets a text field to the display name of a user read from a user custom field, is flagged as having errors:​

Remember, despite the STC error, the script will still run successfully.

The only information that the Jira API gives the STC is that user has the type of java.lang.Object. Fix this by casting the value from the custom field to an ApplicationUser:​

On this page