Scopes Justification

Below we explain why the app requires each of the permissions (scopes) declared in manifest.yml. The descriptions are concise and refer to real usage in the code and the available gadgets.

storage:app

• Save app preferences, feature flags, and temporary results so the app can work faster and remember choices.

• Keep small, app‑specific records that don’t belong to Jira issues or projects.

write:app-data:jira

• Create and update dictionaries, status lists, and other app metadata shared by users and projects.

• Keep global or project‑level switches that control how features behave.

read:jira-work (allowImpersonation: true)

• Show issue details and context inside the app, search by JQL, and validate required fields before creation or updates.

• Display lists, pickers, and summaries based on the user’s visible data.

write:jira-work (allowImpersonation: true)

• Create new issues on behalf of the user, update fields and statuses, and link issues together.

• Save app‑specific attributes to issues (for example, structured properties) to support app features.

read:jira-user

• Show user names and avatars next to issues, comments, and assignments.

• Offer user pickers and readable attributions where appropriate

manage:jira-configuration

• Set up or adjust the Jira configuration required for the app’s features to function correctly.

• Ensure necessary fields, screens, or statuses exist and are available for projects that use the app.

manage:jira-project

• Attach the right screens, workflows, and permissions to projects using the app.

• Store project‑specific settings the app relies on.