Is there a way to retrieve scope change data (#stories, #bugs, #story points, #bug points)

Steve Hooczko March 8, 2023

Is there a way to retrieve scope change data (#stories, #bugs, #story points, #bug points) on a sprint by sprint basis across several sprints in order to track the scope changes and determine if they are for stories (features, enhancements) or bugs (defects)?

1 answer

1 vote
Hitesh March 8, 2023

Hello Steve,

Yes, there are few ways to retrieve scope change data on a sprint-by-sprint basis in Jira as per my knowledge. Here are two approaches:

1) Jira Reports: Jira provides several built-in reports that can be used to track sprint-by-sprint scope changes. One such report is the Sprint Report. The Sprint Report provides a breakdown of issues completed and not completed during a sprint, as well as any changes to scope during the sprint. To generate a Sprint Report:

  • Navigate to your Jira board and click on the "Reports" button.
  • Select "Sprint Report" from the list of available reports.
  • Choose the sprint you want to report on.
  • Review the report, which should show you the number of completed stories, bugs, and story points, as well as any changes to the scope of the sprint.

2) Jira REST API: If you need more detailed data, you can use Jira's REST API to extract data programmatically. You can use the Jira REST API to retrieve issue data, including the issue type (story or bug) and the issue points. Here's an example of how to use the Jira REST API to extract data for a specific sprint:

  • Open a web browser and navigate to the following URL, replacing "YOUR-JIRA-DOMAIN" and "SPRINT-ID" with the appropriate values for your Jira instance and sprint ID:


  • If prompted, enter your Jira credentials to authenticate.
  • The API will return a JSON object containing information about all the issues in the sprint. You can then parse this data to extract the information you need, such as the issue type and points.

Let me know if this helps.




Steve Hooczko March 13, 2023

Thanks. That helps.

Like Hitesh likes this
John Arrowwood March 22, 2024

What is needed is to find where the sprint scope is changed.  The objective is to measure our process and quantify distractions and late-breaking changes.

For example:

This is the set of tickets that were in the sprint as of the start date/time.  That added up to this many story points.

During the course of the sprint, these issues were added to the sprint, totaling this many story points.

Also, during that time, these stories were moved OUT of the sprint, totaling this many story points.  

The data is there in the database.  The question is, how do we get it out without fetching every single ticket and analyzing its worklog and change history?

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events