Sprint Scope for Jira

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

Screens read Jira with the identity of the person viewing them, and check that person's access to the project before showing anything. The app's own identity is used only to build the index of movements and to answer JQL functions, whose results Jira then filters by each user's permissions. The app holds no credentials of its own: there is no API token, no password and no secret to leak.

Encryption

The data the app keeps is held in Forge hosted storage, which Atlassian encrypts in transit and at rest under the Atlassian cloud data encryption policies. Exchanges with Jira go through the Forge platform and never pass through a server run by the publisher.

Vulnerability management

Before every release, the code is scanned with Atlassian's Forge Security Requirements Tester and the dependencies with npm audit; findings are fixed before the release ships, and dependencies are kept up to date.

A vulnerability reported through the Atlassian Marketplace security program or by email is fixed within the timelines of the Atlassian Marketplace security bug fix policy. In case of a security incident or a critical vulnerability, customers and Atlassian are notified.