Cairnscope

Find Jira issues added or removed after a sprint starts

Jira has no built-in JQL for issues added to or removed from a sprint after it started. Mid-Sprint Changes for Jira gives you that list, plus who made each change and when.

Copy these into issue search

Open issue search, switch to JQL, or edit a saved filter, and paste one of these.

Issues added after the sprint started:

issue in addedAfterSprintStart("Sprint name")

Issues removed from the sprint after it started:

issue in removedFromSprint("Sprint name")

Issues in sprints that started between two dates (a sprint scope change report by date):

issue in sprintStartedBetween("2026-01-01", "2026-01-31")

Use the sprint name or number. Names match regardless of case when only one sprint has that name. If two sprints share a name, add the board number as a second argument, or use the sprint number. Dates without a time use the Jira site time zone.

The same examples are in Jira under Apps → Mid-Sprint Changes for Jira.

Add the gadget in three steps

  1. On a dashboard, choose Add gadget and search for Mid-sprint changes.
  2. Add it, pick a sprint, and save. That is the only setup step.
  3. The gadget opens on the counts, then lists each change with the issue, who made it, and when.

The first look at a sprint can take about a minute while history is built. After that, saved filters usually update within about a minute. The gadget shows the newest 50 rows, then “plus N more.”

FAQ

What counts as added? Issues already in the sprint when it started are committed. They do not count as added. An issue counts as added only if it entered the sprint after the start. An issue added mid-sprint and later removed appears in both lists, labelled “later removed” on the added row. An issue removed and later put back is labelled “later re-added” on the removed row.

What if the sprint start date was backdated? The app uses the sprint’s current start date. If a sprint was started before the app was installed and its start date was set earlier than the real start, an issue placed before the real start can show as added. Use the sprint number if a name is ambiguous, and write to support@cairnscope.com if a live sprint looks wrong.

Do subtasks roll up to the parent? No. Subtasks count on their own. A subtask added later is listed even if its parent was planned at the start.

What if there are more than 1,000 results? The function explains how to narrow the search, or how to page through results 1,000 at a time. Add a project clause, or pass a page number as the third argument, for example addedAfterSprintStart("Sprint name", "", "1").

Who can see the issues? You only see issues you can already view in Jira. The gadget reads as you. Other people do not gain access through the app.

Does any data leave Atlassian? No. The app runs on Atlassian. It stores only Jira IDs, sprint metadata, and function arguments. It does not store names, emails, or account IDs. “Who” is read live, under your permissions. See the privacy policy.

Need a hand? Email support@cairnscope.com. More contact details are on the support page.