Installing Sprint Pack shows these scopes. What each one is for:
| Scope, as the install screen names it | What Sprint Pack uses it for |
|---|---|
View Jira issue data (read:jira-work) |
Reading issues’ sprint history and searches, and running the JQL functions |
View user profiles (read:jira-user) |
The display name of whoever made a change, cached for a day |
View sprints (read:sprint:jira-software) |
Each sprint’s dates, state and goal |
View board scope and board settings (read:board-scope, read:board-scope.admin) |
A board’s columns, estimation field and filter, which decide what counts as completed |
Create and delete board settings (write:board-scope.admin, delete:board-scope.admin) |
Writing and removing the app’s own board properties: published BI data, and a marker that lets Jira say whether you administer a board. Never issues |
View projects (read:project:jira) |
The projects the boards use, and their role members for the “from outside the team” guess |
| View screens, screen schemes, screen tabs and screen fields | The admin page’s “Fields on issues” check: which screens show the 8 fields |
View issue details (read:issue-details:jira) |
A work type’s create and edit fields, for the same check on team-managed projects and as the fallback on company-managed ones |
Read and write app data (read:app-data:jira, write:app-data:jira) |
The app’s own 8 fields and its stored search results |
App storage (storage:app) |
The app’s storage on your site, where the sprint history lives |
Report personal data (report:personal-data) |
Reporting the account IDs it stores to Atlassian once a week and erasing closed accounts (privacy policy) |
Not asked for: editing issues (write:jira-work), managing projects, users or settings (manage:*), or any connection outside Atlassian.
Email security@sprintpack.weavecommons.com with the steps to reproduce it. We’ll reply within 3 business days and keep you posted until it’s fixed. Please don’t test against Jira sites you don’t own.