OVERALL RATINGS
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appSee which issues entered or left a sprint after it started
Catch scope creep as it happens
See exactly which issues were added to or dropped from a sprint after it started, who moved them and when. Then compare what the team committed to with what it delivered.
Spot the pattern across sprints
Two charts over your last twelve sprints show how much work slips in or out, and how much of the commitment actually gets done. Export it to Excel for your retrospective.
Bring scope changes into any filter
Four JQL functions put the same data in your filters, boards and automation rules. One line is enough to list every issue added mid-sprint.
Supporting media
More details
Runs on Atlassian: the app runs entirely on Atlassian Forge and no data leaves Atlassian infrastructure. Every Jira permission it asks for is read-only; it never writes to issues, sprints or boards. It stores no personal data: the name of the person who moved an issue is read from Jira when a report opens, and never kept. No configuration: on installation it reads the sprint history already in your site, then follows changes as they happen. Interface in English and French. Known limits: sub-tasks follow their parent and are not counted on their own, story points are counted as they stand today, and sprints closed more than 18 months ago are not indexed.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy and security questionnaire has been filled by the partner
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Sprint Scope for Jira integrates with your Atlassian app
Version information
Version 2.10.0•for Jira Cloud
- Release date
- Sep 30th 2026
- Summary
- Permission checks before any data is read on a user's behalf
- Details
- The project report now checks your Browse Projects permission through the Jira permissions API before doing any work.
- Board, sprint and issue reads are made with your own Jira identity, so Jira applies your permissions.
- Sprint dates are read from the app's index instead of Jira, which removes one call per report.
- Payment model
- Paid via Atlassian
- License type
- Commercial