Jira Subtask Board - Permission Scopes Documentation
Overview
The Jira Subtask Board app requires specific permission scopes to function correctly within your Jira Cloud instance. This document explains each permission scope, why it is needed, and how it is used by the app.
Important: All permissions are used solely for the app's intended functionality. The app does not collect, share, or transmit any data outside of your Jira instance. All data remains within Atlassian's secure infrastructure.
Permission Scopes Explained
1. storage:app
Purpose: Store app configuration settings
Aspect | Details |
|---|---|
What it does | Allows the app to store global settings in Forge's secure app storage |
Why it's needed | Stores the "enabled by default" setting that controls whether the Subtask Board is automatically available for new projects |
Data stored | A single configuration object containing app preferences |
Security | Data is stored in Atlassian's encrypted Forge storage, isolated per installation |
2. read:jira-user
Purpose: Identify the current user
Aspect | Details |
|---|---|
What it does | Reads basic information about the currently logged-in user |
Why it's needed | Displays the current user's name and avatar in the interface, and identifies who is performing actions |
Data accessed | Display name, account ID, avatar URL |
Security | Read-only access to current user only; cannot access other users' private data |
3. read:jira-work
Purpose: Read issues and work items
Aspect | Details |
|---|---|
What it does | Provides general read access to Jira work items |
Why it's needed | Core permission required to display issues and subtasks on the board |
Data accessed | Issue summaries, statuses, and basic work item data |
Security | Read-only; respects Jira's existing permission schemes |
4. write:jira-work
Purpose: Create and update issues
Aspect | Details |
|---|---|
What it does | Allows creating, updating, and managing issues |
Why it's needed | Enables core board functionality: creating subtasks, changing status via drag-and-drop, updating assignees, and modifying issue properties |
Operations enabled | Create subtasks, update issue fields, change status, delete issues, assign/unassign users |
Security | All write operations respect Jira's permission schemes; users can only modify issues they have permission to edit |
5. read:board-scope:jira-software
Purpose: Read board configuration
Aspect | Details |
|---|---|
What it does | Reads the configuration of Jira Software boards |
Why it's needed | Retrieves board column configuration to display the correct status columns on the Subtask Board |
Data accessed | Board columns, column mappings, board layout |
Security | Read-only access to board structure |
6. read:board-scope.admin:jira-software
Purpose: List available boards
Aspect | Details |
|---|---|
What it does | Lists all boards associated with a project |
Why it's needed | Allows users to select which board's configuration to use for the Subtask Board view |
Data accessed | List of board names and IDs for the current project |
Security | Read-only; only shows boards the user has access to |
7. read:project:jira
Purpose: Read project properties
Aspect | Details |
|---|---|
What it does | Reads project-level properties and settings |
Why it's needed | Retrieves saved board colors, display settings, and team capacity configurations stored at the project level |
Data accessed | Custom app properties stored on the project |
Security | Read-only access to project metadata |
8. read:issue-details:jira
Purpose: Read complete issue information
Aspect | Details |
|---|---|
What it does | Provides detailed access to issue data including all fields |
Why it's needed | Displays comprehensive issue information on cards (summary, description, priority, assignee, story points, etc.) and retrieves available status transitions |
Data accessed | Full issue details, custom fields, transitions |
Security | Read-only; respects issue-level security schemes |
9. read:jql:jira
Purpose: Execute search queries
Aspect | Details |
|---|---|
What it does | Allows executing JQL (Jira Query Language) searches |
Why it's needed | Searches for issues and subtasks to display on the board, filters by sprint, parent issue, and other criteria |
Data accessed | Search results based on JQL queries |
Security | Search results are filtered by user permissions; users only see issues they have access to |
10. read:issue:jira-software
Purpose: Read software-specific issue data
Aspect | Details |
|---|---|
What it does | Provides access to Jira Software-specific issue information |
Why it's needed | Reads sprint associations, board-specific data, and agile-related issue properties |
Data accessed | Sprint memberships, agile fields |
Security | Read-only access |
11. read:sprint:jira-software
Purpose: Read sprint information
Aspect | Details |
|---|---|
What it does | Reads sprint data from Jira Software boards |
Why it's needed | Displays active and future sprints, allows filtering the board by sprint |
Data accessed | Sprint names, states (active/future/closed), dates |
Security | Read-only access to sprint metadata |
12. read:epic:jira-software
Purpose: Read epic information
Aspect | Details |
|---|---|
What it does | Reads epic data from boards |
Why it's needed | Displays epic information for issues, enables epic-based filtering and grouping |
Data accessed | Epic names, colors, associations |
Security | Read-only access |
13. read:filter:jira
Purpose: Read quick filters
Aspect | Details |
|---|---|
What it does | Reads quick filter configurations from boards |
Why it's needed | Displays and applies the same quick filters available on your Jira boards |
Data accessed | Filter names and JQL queries |
Security | Read-only; only accesses filters on boards the user can view |
14. write:issue:jira-software
Purpose: Update agile-specific issue properties
Aspect | Details |
|---|---|
What it does | Allows updating Jira Software-specific issue fields |
Why it's needed | Enables updating story point estimates and issue ranking (drag-and-drop reordering) |
Operations enabled | Update estimation, change issue rank/order |
Security | Respects Jira permission schemes |
15. manage:jira-configuration
Purpose: Manage app display conditions
Aspect | Details |
|---|---|
What it does | Allows setting app-level entity properties |
Why it's needed | Controls which projects show the Subtask Board tab based on admin configuration |
Data managed | App visibility settings per project |
Security | Only affects this app's display conditions |
16. manage:jira-project
Purpose: Store project-level app settings
Aspect | Details |
|---|---|
What it does | Allows reading and writing project entity properties |
Why it's needed | Stores board customizations: custom card colors, board display settings, and team capacity configurations |
Data managed | App-specific settings stored as project properties |
Security | Only manages properties namespaced to this app; does not affect core Jira project settings |
Security & Privacy Summary
What the app CAN do:
Read issues, boards, sprints, and epics you have access to
Create and update subtasks within your permission level
Store app settings in Atlassian's secure storage
Display information from your Jira instance
What the app CANNOT do:
Access data you don't have permission to see
Bypass Jira's permission schemes
Export or transmit data outside Atlassian infrastructure
Access other Atlassian products or external services
Modify core Jira settings or configurations
Access other users' private data
Data Handling:
No external data transmission: All data stays within Atlassian's infrastructure
No data collection: The app does not collect analytics or usage data
Isolated storage: App settings are stored in Forge's encrypted, isolated storage
Permission-respecting: All operations respect your existing Jira permission schemes
Frequently Asked Questions
Q: Can the app see private issues I don't have access to?
A: No. The app operates under your user context and can only see issues you have permission to view.
Q: Does the app send data to external servers?
A: No. The app runs entirely within Atlassian's Forge platform. No data leaves Atlassian's infrastructure.
Q: Can the app modify my Jira project settings?
A: No. The manage:jira-project scope only allows storing app-specific properties (like card colors). It cannot modify your project's core configuration.
Q: Why does the app need write permissions?
A: Write permissions enable the core board functionality: creating subtasks, dragging cards to change status, updating assignees, and reordering issues.
Q: What happens if I revoke permissions?
A: The app will lose functionality corresponding to the revoked permissions. For example, revoking write permissions would make the board read-only.
Contact & Support
If you have questions about these permissions or the app's functionality, please contact the app developer or visit the app's support page in the Atlassian Marketplace.