Quick start
Use this guide for the first review in a Jira project. The separate review kit includes a 10-minute meeting agenda.
First review
Sprint Scope Guard reads the active or planned Scrum sprint associated with the Jira project where you open it. It does not create a sample sprint or substitute missing data.
An Atlassian or Jira site administrator installs the app from the Atlassian Marketplace. If you cannot access the installation controls, ask that administrator to install it. Then open the Jira project you want to review and select Sprint Scope Guard from that project’s navigation. Use the project that owns the Scrum board and sprint.
Review remaining pre-start work, injected work, and removals. The remaining baseline is the work still in the sprint from before it began; it is not an original commitment snapshot. With recognised estimates, totals use story points. Otherwise, use the displayed ticket counts.
Discuss the items added after start. Authorized project users can approve an addition, return an injected item to the backlog, or exchange it for baseline work with a scope swap. If you only need a record, leave Jira unchanged and document the decision.
Export the displayed audit as CSV or JSON. The Retro report can be copied or downloaded as Markdown. These exports are created locally in the browser; they are not sent to a separate Sprint Scope Guard service.
Optional: saved filters
The functions below accept a required project key. They are useful for filters and dashboard gadgets after the app has refreshed its current data.
issue in addedToSprintAfterStart("PROJECT_KEY")issue in removedFromSprint("PROJECT_KEY")issue in hasUnresolvedSubtasks("PROJECT_KEY")Results can be eventually consistent while Jira event updates and the hourly reconciliation run.
When the page is empty or unavailable
The app has nothing to classify yet. Start or plan a Scrum sprint on the relevant board, then refresh the page.
Ask the site administrator to check the app’s Marketplace subscription and billing state in Atlassian administration. When the license is active, reopen or refresh the project page.
Refresh the project page, then confirm that the person opening it can read the project, board, sprint, and issues in Jira. If the message remains, check the administrator guide and contact Neural Void support with the visible error details.