Administrator guide

Review the data boundary before installing.

Sprint Scope Guard is a Jira Cloud Forge app. Its released artifact reads Jira data, stores limited action records in Forge Storage, and has no external backend destinations, telemetry, or webhooks.

Review on MarketplaceRead quick start

Declared capability

What the app requests.

The Forge manifest asks Jira for exactly the access needed to read current scope, make authorized scope changes, run its JQL functions, and store its own limited app data.

Read from Jira

  • read:jira-work and read:issue-details:jira for issues and their relevant history.
  • read:sprint:jira-software and read:board-scope:jira-software for the current project board and sprint.
  • read:project:jira, read:jql:jira, and read:app-data:jira for project context, JQL, and app data.

Write when authorized

  • write:board-scope:jira-software to move selected issues to the backlog for a revert or scope swap.
  • write:app-data:jira and storage:app to store governance records and administrator settings in Forge Storage.
  • Jira events and hourly reconciliation refresh stored JQL results.

Outside the artifact

  • No external backend destinations.
  • No usage analytics or webhooks. Minimal failure diagnostics are recorded in Forge logs.
  • CSV, JSON, and Markdown exports are created in the viewer’s browser.

Permission checks

Reads follow Jira visibility; writes are verified on the server.

The app does not grant a user access to Jira objects that Jira does not allow that user to see.

Administrator settings

Saving settings requires Jira project-administrator permission for the current project.

Scope actions

Approve, return-to-backlog, and scope-swap actions verify the current project and issue server-side, and require Jira EDIT_ISSUES, SCHEDULE_ISSUES, or project/instance administrator permission.

JQL functions

Each custom function requires a valid Jira project-key argument. It does not infer a project from an omitted argument.

Storage and retention behaviour

Limited action records, not a history product.

The product reports the current sprint. It does not expose closed-sprint history or create an original commitment snapshot.

Governance records

For an approval, revert, or scope swap, the app stores a record bound to its project and sprint. Arrays of approved issues, reverts, and swaps are bounded to 100 entries each.

Removal display

A removal record can outlive a viewer’s Jira access. Before showing it, the app re-fetches readable issue information from Jira as that viewer; it does not return stored historic issue copies.

Uninstall and recovery

Uninstall Sprint Scope Guard through your Atlassian administration app-management workflow. Forge-hosted storage is retained for 28 days after uninstallation. A reinstall does not restore it automatically; an app developer can request a re-link with customer consent within 21 days of uninstall. See Atlassian’s Forge storage reference. For product help, use Neural Void support.

Operational limits

Set expectations with the team.

Eventually consistent JQL

Jira events refresh stored query results. An hourly reconciliation covers missed updates, so a saved filter may not reflect a scope action immediately.

Current scope only

The trends view reports the current sprint only. It does not forecast a failure date, simulate future changes, use AI, or infer root causes.