Retrieve issues by Sprint -- WHICH WERE MOVED FROM A PREVIOUS ONE

[Timothy Fischer]

I've noticed that I'm not getting issues that are in a current sprint that were moved over from previous ones. 

The REST API I'm calling is:

string jiraUrlEnd = $"/rest/agile/1.0/board/{boardId}/sprint/{sprintId}/issue?startAt={startAtNumber}";

Is there some sort of change that I need to make to the request so it looks something like this:

/rest/agile/1.0/board/{boardId}/sprint/Issue in={sprintId}/issue?startAt={startAtNumber}";

Please let me know how I can get these issues.

Thanks,

Tim

[Earl McCutcheon · Accepted solution]

Hello @Timothy Fischer ,

When using the Get issues for sprint API endpoint:

• GET /rest/agile/1.0/sprint/{sprintId}/issue

You should see all the issues that have been assigned to that sprint that the user has permission to view. I did a quick test on my staging instance and using this method I did receive issues that were in the current sprint but also in multiple previous sprints as well.

so initially I would say to verify that the issues in the previous sprints belong to the same project as the new sprints and that all the permissions line up.

But additionally looking at your call you are using a start at variable "?startAt={startAtNumber}".  Are you possibly missing either the initial issues in the sprint by starting at a higher interval OR missing th e higher values by missing a max result variable?

I'd recommend checking out Eve's status update in the following request noting some rate-limiting conditions that may be a factor here:

•  https://jira.atlassian.com/browse/JRACLOUD-67570

Then in turn the documentation on Changing maxResults parameter for Jira Cloud REST API to get around this limitation.  I hope this helps.

Regards,
Earl