Issue Manager getIssueObject oddity

[Ron Gates]

I was working on script for a Custom Listener (using Jira 7.3 and ScriptRunner 4.3) and noticed that following piece of code works:

import com.atlassian.jira.component.ComponentAccessor

def issueKey = "JIRA-1234";
def issueManager = ComponentAccessor.getIssueManager()
def issueObject = issueManager.getIssueObject("JIRA-1234")
def issueObjectID = issueObject.getId()

But when:

def issueObject = issueManager.getIssueObject("KEY-1234")

is being replaced by:

def issueObject = issueManager.getIssueObject(issueKey)

The code just assigns null to the issueObject variable and code returns following error:

java.lang.NullPointerException: Cannot invoke method getId() on null object

So in other words when the issue key is used directly as parameter for getIssueObject method - the code works. But when variable is used as a parameter - the code doesn't work.

Any idea why this is happening?

In the meantime, I have circumvented this problem using Search Provider (I share workaround in case somebody has similar problem and needs working solution):

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.jql.parser.JqlQueryParser
import com.atlassian.jira.issue.search.SearchProvider
import com.atlassian.jira.web.bean.PagerFilter

def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser);
def searchProvider = ComponentAccessor.getComponent(SearchProvider);
def authContext = ComponentAccessor.getJiraAuthenticationContext();
def issueKey = "JIRA-1234";
def jqlQuery = jqlQueryParser.parseQuery(issueKey);
def user = authContext.getLoggedInUser();
def results = searchProvider.search(jqlQuery, user, PagerFilter.getUnlimitedFilter());
def issues = results.getIssues();
def issueObject = issues[0];
def issueObjectID = issueObject.getId();

But still would like to know why getIssueObject method is not working with string variable.

Thanks in advance for clarifying this oddity for me!

[Daniel Yelamos [Adaptavist] · Accepted solution]

Hello.

I have set up a test environment and it seems to work. I have attached this customlistener to every issue event. As you can see here:

Could you tell us which event you are attaching the listener to so that we are able to give it a try?

Cheers!

[Ron Gates]

Thank you for testing!

The Custom Listener I have defined triggers on "Issue Resolved" event.

Jira that I am testing this on is v7.3.0.

Maybe there is a problem with that specific version of Jira - what version are you using?

[Daniel Yelamos [Adaptavist]]

Hi Ron.

Glad to run some testing for you. We checked out different jira versions, 7.3.0, and 7.3.3 and in both cases it worked. We realized that in your issue, we see that in the original question, you have:

def issueKey = "JIRA-1234";

however, you say it does not work when:

def issueObject = issueManager.getIssueObject("KEY-1234")

We've noticed that the two keys are different. Could this be the cause of your issue? 

[Ron Gates]

Thanks for some more testing!

I am glad this works in general and causing problem only for me.

I use actual project key from our Jira instance - the "JIRA-1234" and "KEY-1234" are just examples.

Problem still persists for me but I have a workaround (I shared it in the initial post - so I'm good).

Also this hopefully won't be a problem soon as we migrate to different Jira instance (and I hope this problem will disappear).

[Dante Labate]

It works!

def issueKey = "JIRA-1234";
def issueManager = ComponentAccessor.getIssueManager()
def issueObject = issueManager.getIssueObject("${issueKey}")

[Nic Brough -Adaptavist-]

It looks like it doesn't think it's a string.

[Ron Gates]

Official Jira docs says it needs to be a String:

https://docs.atlassian.com/jira/server/com/atlassian/jira/issue/IssueManager.html#getIssueObject-java.lang.String-

But even after explicitly specifying type of the variable or converting it to string the error persist.

Go figure...