Sprint Scope for Jira

How to use it · Last updated: 22 September 2026 · Privacy and security

See what entered or left a sprint

  1. Open the project.
  2. In the project navigation, click Sprint scope. Depending on your screen width and the project type, it sits in the tabs at the top, in the left menu, or folded under More.
  3. Pick a sprint from the dropdown.

Four figures appear at the top: pulled in, taken out, those that did both, and the net change in points. The two tables below list the issues, with the name of the person who moved them and the date.

An issue can appear in both tables. It is then marked "in and out". Click an issue key to open it.

Below the figures, Committed and completed compares the points the team had in the sprint when it started with the points it finished in that sprint:

  • Committed at start: issues in the sprint when it started. The app rebuilds this list from the sprint's content and the movements it recorded.
  • Completed: issues in a done status that were not carried over to a later sprint. During a running sprint, this reads Completed so far.
  • Completion rate: completed points over committed points.

Sub-tasks are left out, and points are counted as they stand today.

Compare several sprints

On the same page, open the Across sprints tab.

The first chart shows story points pulled in and taken out across the project's last twelve sprints. The second compares committed and completed points for the same sprints. The table below gives every figure, including each sprint's net change and completion rate.

Get the data into Excel

On either tab, click Export to Excel. The file downloads straight away and opens in Excel, LibreOffice or Google Sheets.

  • From a sprint: a Summary sheet with the figures, and an Issues sheet with one row per movement: direction, issue key (a link to the issue), summary, points, status, assignee, who moved it and when.
  • From the trend tab: one row per sprint with every figure shown on screen.

Filters are already set on the header row, and dates are real dates you can sort.

Add the chart to a dashboard

  1. Open a Jira dashboard.
  2. Click Edit, then Add gadget.
  3. Find Sprint scope change and add it.
  4. In the gadget settings, pick the board to follow, then save.

The gadget shows points pulled in and taken out across that board's last eight sprints.

Use the data in a filter or an automation rule

Write one of these functions in any Jira search:

issue in sprintScopeAdded("Sprint 42")
issue in sprintScopeRemoved("Sprint 42")
issue in sprintStartedBefore("2026-01-15")
issue in sprintEndedBefore("2026-01-29")

Write the sprint name in quotes, exactly as it appears in Jira. The date functions look at the sprint, not the issue: they return every issue of the sprints that started, or were closed, before that date. A sprint still open never counts as ended, even past its planned end date.

To follow the running sprint without editing the filter every fortnight:

issue in sprintScopeAdded("currentSprint(MOBL)")

where MOBL is your project key.

Show the entry date as a column

The Pulled into sprint field holds the date an issue entered its sprint, when that happened after the start.

A Jira administrator has to switch it on once:

  1. Jira settings, then Issues, then Custom fields.
  2. Find Pulled into sprint.
  3. Open the row menu and choose Associate to screens.
  4. Tick the screens of the relevant projects.

After that, anyone can add it as a column from the column picker in a search.

If data seems to be missing

Open Jira settings, then Apps, then Sprint scope.

That page shows the state of the initial sync, the project being processed and how many issues have been read.

  • Running: wait, the bar is moving.
  • Waiting on Jira: Jira is temporarily rate-limiting the app. It resumes on its own, and the page gives the time.
  • Done: the data is up to date. If a sprint still looks incomplete, click Run the sync again.

Run the sync again after importing issues in bulk as well.

What the app cannot recover

  • An issue removed from a sprint with no trace in its history. This happens on instances migrated from Jira Server or filled by bulk import.
  • Sub-tasks do not count as movements: they follow their parent issue.
  • Sprints closed more than 18 months ago are not tracked.
  • Story points are shown as they stand today. An issue re-estimated afterwards distorts the total.

Support

Questions, bugs or feature requests: open the support page or write to contact@goth-tech.fr.