Are there any alternatives for the API rest/greenhopper/latest/rapid/charts/sprintreport

Question

I found that the rest/greenhopper/latest/rapid/charts/sprintreport returns many useful information like completedIssues, issuesNotCompletedInCurrentSprint, issuesCompletedInAnotherSprint, issueKeysAddedDuringSprint, puntedIssues

I searched in the community and I found that greenhopper is not recommanded to used. And as I didn't find document for latest greenhopper apis, therefore I'm not sure if it supports oauth 2.0 and what scope is required. So maybe I should not use this API for getting this information?

But on the other hand, I checked issue related api https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-post and sprint related apis https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-group-sprint, I did not find any field looks like completedIssues, issuesNotCompletedInCurrentSprint, issuesCompletedInAnotherSprint, issueKeysAddedDuringSprint, puntedIssues in the rest/greenhopper/latest/rapid/charts/sprintreport. I'm wandering if there's and alternatives or workaround to get these information?

Thanks a lot!

Apryl Harris · Answer

Hi,
Has anyone figured out an automation rule that will populate some custom field so we can get the "committed" work items at the start of a sprint via JQL?

Bill Sheboy · Answer

Hi @Qedi Testing -- Welcome to the Atlassian Community!

I believe those old Greenhopper endpoints are unsupported now.  And as they apparently used the issues' history to calculate those measures, two alternatives are:

* Investigate marketplace apps which can do this, also using the histories
* Use automation rules and custom fields (or entity properties on the sprint) to gather the measures.  This will require multiple rules with the sprint-related triggers, and is subject to count errors when someone tampers with the sprint assignments to the issues.

Kind regards,
Bill

Satish Venkata Sesetty · Answer

Hello @Qedi Testing ,

we have workaround for this with Jira automation.

For Completed issues : create automation like this when sprint is completed (Mention the board details) then use branch (for issue in sprint) then edit  the ticket and set the end date as {{now}} and write JQL like this "  Sprint = XXXX and "end date" is not empty  "

issuesNotCompletedInCurrentSprint : for this you can write query "  Sprint = XXXX and "end date" is  empty  "

Like this you can find the tickets.

Thanks