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

Scriptrunner Cannot find matching method ProjectManager#getProjectObjByKey

Daniel Neville February 1, 2019

JIRA version is 7.4.2

Scriptrunner version is 5.4.48

Here's some sample code:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.IssueFactory
import com.atlassian.jira.project.ProjectManager
import groovy.transform.Field
import com.atlassian.jira.issue.MutableIssue

@Field IssueFactory issueFactory = ComponentAccessor.getIssueFactory()
@Field ProjectManager projectManager = ComponentAccessor.getProjectManager()

String createOperationalAlarmIssue(alarmObject) {
MutableIssue newTask = issueFactory.getIssue()
newTask.setDescription(alarmObject["description"])
newTask.setProjectObject(
projectManager.getProjectObjByKey(alarmObject["bucket"])
)
}

And I get these errors: 

[Static type checking] - Cannot find matching method com.atlassian.jira.issue.MutableIssue#setDescription(java.lang.Object). Please check if the declared type is correct and if the method exists.

[Static type checking] - Cannot find matching method com.atlassian.jira.project.ProjectManager#getProjectObjByKey(java.lang.Object). Please check if the declared type is correct and if the method exists.

[Static type checking] - Cannot find matching method com.atlassian.jira.issue.MutableIssue#setProjectObject(java.lang.Object). Please check if the declared type is correct and if the method exists. 

What am I missing here?

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
Marc Minten _EVS_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 6, 2019

Do not understand your example, but

...these are just static type checks. Groovy does not know the type of "alarmObject" nor of "alarmObject['...']" (you did not tell him), so considers it as a general object.

But in fact Groovy only needs the correct type at run time so you should not worry about these "errors". If you want to get rid of them, indicate the type of the method arguments...

Daniel Neville February 6, 2019
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.IssueFactory
import com.atlassian.jira.project.ProjectManager
import groovy.transform.Field
import com.atlassian.jira.issue.MutableIssue

@Field IssueFactory issueFactory = ComponentAccessor.getIssueFactory()
@Field ProjectManager projectManager = ComponentAccessor.getProjectManager()

String createOperationalAlarmIssue(alarmObject) {
MutableIssue newTask = issueFactory.getIssue()
String description = alarmObject["description"]
newTask.setDescription(description)
String bucket = alarmObject["bucket"]
newTask.setProjectObject(
projectManager.getProjectObjByKey(bucket)
)
}

Declaring the argument type beforehand solved the issue. I was thrown by the "method not found": but I'm coming to this from a Python background, so perhaps this is a standard error that a Java dev would recognize immediately. 

TAGS
AUG Leaders

Atlassian Community Events