ScriptRunner/Groovy Cannot invoke method getSprintsForView() on null object

Question

I'm attempting to use a ScriptRunner/Groovy script to give me a list of active and open (in progress & future) sprints in a specific board. For some reason, whenever I use the getSprintsForView() method, it fails and errors "cannot invoke method getSprintsForView() on null object".

The odd thing is that I check if the view is null, and the view seems to work just fine with other methods (like getOpenSprintsAndBacklogProjects.

import com.atlassian.jira.component.ComponentAccessor;
import com.atlassian.greenhopper.service.rapid.view.RapidViewService;
import com.atlassian.greenhopper.service.rapid.RapidViewQueryService;
import com.atlassian.greenhopper.model.rapid.RapidView;

import com.atlassian.greenhopper.service.sprint.Sprint;
import com.atlassian.greenhopper.service.sprint.SprintManager;

def sprintManager = ComponentAccessor.getOSGiComponentInstanceOfType(SprintManager.class);
def rapidViewService = ComponentAccessor.getOSGiComponentInstanceOfType(RapidViewService.class);
def rapidViewQueryService = ComponentAccessor.getOSGiComponentInstanceOfType(RapidViewQueryService.class);

board_id = 89L;

def sprints = [];
def sprints_two = [];

def view = rapidViewService.getRapidView(user, board_id).getValue();

if (view != null)
{
  sprints = rapidViewQueryService.getOpenSprintsAndBacklogProjects(user, view).getValue().left();  
  sprints_two = sprintManager.getSprintsForView(view).getValue();
}

What am I doing wrong?

harainye · Answer

it works!

thank you so much!

Thanos Batagiannis _Adaptavist_ · Answer

What if you try to get the sprintManager like

import com.atlassian.greenhopper.service.sprint.SprintManager
import com.onresolve.scriptrunner.runner.customisers.PluginModuleCompilationCustomiser

SprintManager sprintManager = PluginModuleCompilationCustomiser.getGreenHopperBean(SprintManager)

Please let me know if this does the trick.

Regards, Thanos

ludwigbayer · Answer

That is indeed what was happening. SprintManager is apparently not exposed in the Jira API.

As someone new to this type of work, it was unfortunately not very obvious this is the case from the API documentation.