Punted issues in sprint report

[V P Kavya]

Upon the transition of tickets from the "In Review" status to the "Ready for Testing" status, an observation pertinent to our project has been made. Specifically, it has been noted that the issues residing in the "Ready for Testing" status are relocated and categorized under the "punted issues" section within the sprint report. Consequently, it raises the question of whether the "punted issues" field is also designated to encompass the issues that have been removed from the current sprint. The introduction of this practice, wherein tickets that remain within the sprint are placed under the "punted issues" category, has given rise to difficulties in accurately calculating the scope change. In light of these circumstances, any assistance and elucidation regarding the specifics of "punted issues" would be immensely appreciated.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

What does "punted issues" mean?  What is it in your Jira?

[V P Kavya]

We are ingesting data for issues using this api endpoint

"/rest/greenhopper/latest/rapid/charts/sprintreport"

and it gives us the sprint report. punted issues is a field inside this returned document 

In Jira, the term "punted issues" refers to issues that were originally planned for a specific version or sprint but were postponed or deferred to a later date. Punting an issue typically means that it will not be addressed in the current release or sprint and will be moved to a future release or backlog.

[Nic Brough -Adaptavist-]

Ah, you're looking at a deprecated API, there's no point looking at that.

[V P Kavya]

Oh okay, can you please let me know which is the alternative API endpoint that can be used instead ?