Sprint History for Jira

Four JQL functions that answer what Jira's own JQL can't: what happened to a sprint's scope. Jira's WAS and CHANGED operators don't support the Sprint field (JRACLOUD-75868, JRACLOUD-72007); these functions fill that gap.

Functions

Query	Returns
`issue in removedFromSprint(42)`	Issues taken out of sprint 42 and not put back
`issue in addedAfterSprintStart(42)`	Issues added after sprint 42 started (and before it closed)
`issue in wasRemovedFromSprint(42)`	Issues removed from sprint 42 at any point, even if re-added
`issue in sprintChurn(42)`	Added late or removed: all scope change

Each function takes a numeric sprint ID, shown on the app's Status tab or in the sprint report URL. Use them with in and not in in issue search, filters, boards, dashboards and subscriptions. Results follow each user's Jira permissions.

Getting started

Install the app. It starts recording Sprint field changes and begins reading existing Sprint history.
In issue search, type issue in removedFromSprint(<sprint ID>).
Optional: limit the history read to some projects under Configure → Settings.

Example queries

issue in removedFromSprint(42)
issue in addedAfterSprintStart(42) AND type = Bug
issue in wasRemovedFromSprint(42) AND issue not in removedFromSprint(42)
issue in sprintChurn(42) AND project = ABC ORDER BY updated DESC

Admin

Go to Jira settings → Apps → Sprint History → Configure.

Status: index health, the last recorded change, and sprint IDs.
Backfill: reads existing Sprint history. Starts on install; Pause, Resume and Re-run controls.
Settings: an optional JQL to limit which issues the backfill reads.
Get started: example queries.

Limits

A function returns at most 1,000 issues. Above that, add conditions such as project = ABC.
Changes usually show up within seconds. Allow up to 5 minutes.
While the backfill is running, sprints it hasn't reached yet return only changes recorded since install.

FAQ

Does a sprint closing count as a removal? No. Jira keeps the closed sprint on unfinished issues, so carry-over isn't counted.
Sprints that ended before install? Yes, once the backfill reaches them.
What happens on uninstall? The app deletes its stored data.

Data

The app stores issue IDs, sprint IDs, sprint name, state and dates, and change times, all in Atlassian Forge storage. Nothing leaves Atlassian. It stores no issue text and no user data.