App Scopes and Permissions (Security & Privacy)

This application uses Forge and Connect scopes to access Jira data strictly for providing its declared functionality.
All permissions follow the principle of least privilege and are used only to enable SLA management, issue processing, reporting, dashboards, and automation.

The app does not access or store data beyond what is required, and all data is processed within Atlassian-approved environments.

Forge App Scopes (Core)

Used for internal app operation and secure data storage.

• storage:app — Stores application configuration and operational data

• read:app-data:jira — Reads app-specific data from Jira

• write:app-data:jira — Writes and updates app-specific data in Jira

Forge Jira Scopes (Core)

Required for authentication and basic Jira data access.

• read:app-user-token — Accesses user authentication context

• read:app-system-token — Accesses system authentication context

• read:jira-user — Reads Jira user information

• read:jira-work — Reads Jira work data required for app features

Issue Processing for Reporting

Used to collect issue data for reports and analytics.

• read:issue:jira — Reads Jira issues

• read:issue.property:jira — Reads issue properties used for reporting logic

SLA Goal Actions — Comment Creation

Used to automatically create and manage issue comments related to SLA events.

• read:comment:jira — Reads issue comments

• read:comment.property:jira — Reads comment properties

• read:group:jira — Reads user groups for permission checks

• read:project:jira — Reads project and board data

• read:user:jira — Reads user details

• read:avatar:jira — Reads user and system avatars

• read:project-role:jira — Reads project roles

• write:comment:jira — Creates and updates issue comments

• write:comment.property:jira — Updates comment properties

• write:issue.watcher:jira — Manages issue watchers

SLA Goal Custom Fields

Required to create, configure, and manage SLA-related custom fields.

• read:screen:jira — Reads Jira screens

• read:screen-scheme:jira — Reads screen schemes

• read:issue-type-screen-scheme:jira — Reads issue type screen schemes

• read:screen-field:jira — Reads screen fields

• read:screenable-field:jira — Reads available fields

• read:screen-tab:jira — Reads screen tabs

• read:project-category:jira — Reads project categories

• manage:jira-configuration — Creates and manages custom fields

• write:screenable-field:jira — Updates screenable fields

Webhooks

Used to receive Jira events required for real-time SLA and automation processing.

• manage:jira-webhook — Registers and manages Jira webhooks

Dashboard Gadget

Used to display SLA and reporting data on Jira dashboards.

• write:dashboard.property:jira — Stores and updates dashboard gadget properties

SLA Goal Actions — Issue Updates

Used to automatically update issues based on SLA rules.

• write:issue:jira — Creates, updates, and transitions issues

Issue Properties for Filtering

Used to store technical metadata required for filtering and processing issues.

• write:issue.property:jira — Creates and updates issue properties

Sprint Data Access

Used to fetch sprint data for report generation.

• read:board-scope:jira-software — Reads boards associated with sprints

• read:sprint:jira-software — Reads sprint information

Request Type Access (Jira Service Management)

Used to fetch request types for SLA and reporting features.

• read:servicedesk-request — Reads service desk request types

Connect Scopes

Used only where Forge limitations require extended Jira capabilities.

• read:connect-jira — Reads Jira data

• write:connect-jira — Updates Jira issues

• admin:connect-jira — Manages SLA-related configuration

• act-as-user:connect-jira — Performs actions on behalf of the user

• access-email-addresses:connect-jira — Accesses email addresses for report scheduling only

Helpful resources & links