Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,409,321
Community Members
 
Community Events
169
Community Groups

Script Runner Error 'Failed type checking'

I am trying to use script runner to be able to check my scripts for any error/deprecated classes. However for two files simply says that there was an error:

Failed type checking and we don't know why, it's our fault not yours @ line 1, column 1.

 

Is there any possible reason why the it is doing this. I know for a fact there should be some errors indicating deprecated classes since there are a few calls to component manager in there.

UPDATE: Found the following piece of code that is causing the error

Map tmprc = issue.getCustomFieldValue(rcObj) as Map
 if (tmprc) {
 // Root Cause Category field defined but ensure both parts of its cascading field are selected
 rotCausEntered = ((tmprc.get(null) != null) && (tmprc.get("1") != null))
 }

//in particular is is the following bit of code causing the error

(tmprc.get(null) != null)

2 answers

0 votes
JamieA Rising Star Aug 11, 2016

When you say "assembled using make" what does that mean? Can you slim it down to a representative sample?

 

 

Added a representative sample.

 

0 votes

It's the it that's causing this, you say? As in the it variable that exists inside of a Groovy closure?

That's one of the known limitations of the static type checker. The types of Closure parameters cannot be inferred.

See https://scriptrunner.adaptavist.com/latest/jira/#_static_type_checking.

JamieA Rising Star Aug 11, 2016

They can be inferred usually, eg in 

issue.subtasks.collect {it.summary }

but not in 

def c = { it.summary }
issue.subtasks.collect(c)

Suggest an answer

Log in or Sign up to answer