Current manifest scopes
permissions:
scopes:
- read:jira-user
- read:jira-work
- read:project:jira
- read:board-scope:jira-software
- read:sprint:jira-software
- read:issue-details:jira
- read:jql:jira
- read:user:jira
- storage:appScope purposes
| Scope | Purpose |
|---|---|
read:jira-user | Read authorised user display information needed for assignee-oriented reporting. |
read:jira-work | Read Jira work items and related fields required for sprint reports. |
read:project:jira | List and identify Jira projects available to the current user. |
read:board-scope:jira-software | Read Jira Software board information for board selection. |
read:sprint:jira-software | Read sprint names, dates, goals, state and related sprint information. |
read:issue-details:jira | Read authorised issue-level detail used in reports and exports. |
read:jql:jira | Run Jira searches needed to collect issues for the selected report context. |
read:user:jira | Read authorised Jira user details such as display names used in reports. |
storage:app | Store short-lived report caches and per-user fair-use counters in Atlassian-hosted Forge storage. |
No write access
The current manifest does not request Jira write scopes. StatusDeck is designed as a read-focused reporting app and does not modify Jira issues, projects, boards or sprints.
Scope changes
QTI Labs will review, document and minimise scopes. Material additions will be reflected on this page and may require administrator re-consent through Atlassian.
Effective date: upon first public availability of StatusDeck on the Atlassian Marketplace. Review at least annually and after material product, scope, storage, subprocessor, security or legal changes.