Sprint Scope for Jira

What this app stores

Sprint Scope keeps an index of sprint scope movements so that queries answer quickly. For each movement it stores:

• the numeric identifier of the issue and of the sprint,
• whether the issue entered or left that sprint, and when,
• the story point estimate of the issue,
• the name of the sprint.

Short-lived copies

To keep pages fast, it also keeps short-lived copies of sprint and board lists, and per-sprint totals: points committed at the start and points completed.

No personal data

It stores no personal data: no account identifier, no name, no email address. When you open a report, the name of the person who moved each issue is read from Jira at that moment, shown, and not kept.

It does not store issue summaries, descriptions, comments, attachments, or any other issue content.

Where it is stored

Inside Atlassian's own infrastructure, using the Forge storage service, in the region assigned to your Atlassian site. No data is sent to any server operated by GOTH or by any third party. The app holds the Runs on Atlassian badge, which certifies exactly this.

Who can read it

Only your Atlassian site. The app reads Jira data with application permissions and returns issue keys, which Jira then filters according to each user's own permissions. A user never sees, through this app, an issue they could not see in Jira.

How long it is kept

For as long as the app is installed. Sprints closed more than 18 months ago are not indexed. Uninstalling the app deletes its storage, which Atlassian performs on its side.

Hosting and data residency

The app runs entirely on Atlassian Forge and carries the Runs on Atlassian badge. There is no server, no database and no logging service operated by the publisher. Data residency follows your Atlassian site.

Permissions requested

The Jira permissions are read-only: the app never writes to your issues, sprints or boards. storage:app covers only the app's own index, held inside Atlassian.

• read:jira-work: read issues and their change history to reconstruct scope movements.
• read:sprint:jira-software: read sprint start and end dates.
• read:board-scope:jira-software: list the Scrum boards of a project.
• read:project:jira: list projects during the initial sync.
• storage:app: keep the index of movements.

Authentication

Calls to Jira are made with the app's own identity. The app holds no credentials of its own: there is no API token, no password and no secret to leak.