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.

admin:connect-jira

• scope for Connect features/modules

• This scope is essential for administrative operations within Jira. The application provides multiple admin configuration panels including:

  • Customer Actions configuration (/customer-actions)

  • Ticket Journey configuration (/steps-configuration)

  • Additional Fields configuration (/additional-fields-config)

  • Global banner configuration (/banner-config)

access-email-addresses:connect-jira

• scope for Connect features/modules

• Used to retrieve user emails in the feature “Global Banners” when matching users with conditions related to the domain.

read:connect-jira

• scope for Connect features/modules

• This is a fundamental scope required for basic Jira connectivity and reading Jira data. The application extensively reads:

  • Project information for configuration panels

  • Issue data for customer actions and request processing

  • User information for request assignment and processing

  • Service desk configurations for portal customization

• This scope is the foundation for most read operations performed by the application and cannot be removed.

act-as-user:connect-jira

• The app adds comments (via Jira Rest API) as a given user (used in the customer actions feature).

storage:app

• Used in the “Issue Banners” feature for storing configuration. The feature has been moved to another application Service Pack. The scope was kept to avoid triggering a major version update, considering that it will be needed soon (the remaining four features are currently being migrated from Connect to Forge).

read:jira-work

• Used in the “Issue Banners” feature for reading issue details. The feature has been moved to another application Service Pack. The scope was kept to avoid triggering a major version update, considering that it will be needed soon (the remaining four features are currently being migrated from Connect to Forge).

read:jira-user

• Used in the “Issue Banners” feature for reading user information. The feature has been moved to another application Service Pack. The scope was kept to avoid triggering a major version update, considering that it will be needed soon (the remaining four features are currently being migrated from Connect to Forge).

read:servicedesk-request

• Used in the “Issue Banners” feature for reading request information on the portal panels. The feature has been moved to another application Service Pack. The scope was kept to avoid triggering a major version update, considering that it will be needed soon (the remaining four features are currently being migrated from Connect to Forge).