Scopes justification
Feature Bundle declares 17 scopes, which are the permissions it asks Atlassian for. This page explains why the app needs each of them and which feature uses it.
storage:app
Feature Bundle stores the configuration of all its features in Atlassian storage: panels, forms, Ticket Journey steps, announcement banners, and App Configuration.
read:jira-work
Feature Bundle reads requests and their fields to show them in panels and in the edit dialog of a form. It also runs JQL searches to check conditions of panels, forms, and steps, and it reads transitions, projects, statuses, and link types.
write:jira-work
Customer Actions uses this scope when a customer saves a form. The app changes the fields of the request, performs workflow transitions, removes attachments, adds internal comments, and creates and removes links between work items. It also counts the saves of a form against its saving limit.
read:jira-user
Feature Bundle reads the groups, the language, and the email address of a user to decide who sees a banner, a panel, or a form. It also reads the display name of the customer for the automatic comment and searches users for the user picker of a form.
read:servicedesk-request
Feature Bundle reads data of requests on the portal: SLA metrics, approvals, the request view, attachments, request types, and portals.
write:servicedesk-request (with impersonation)
Customer Actions adds a public comment and publishes new attachments to a request in the name of the customer. Impersonation lets the app do this for a customer who has no Jira license.
manage:servicedesk-customer
Feature Bundle reads the organizations of a user and the list of organizations, to decide access by organization and to fill the organization pickers. The app only reads organizations. It doesn’t create or change them.
manage:jira-project
Feature Bundle saves the configuration of panels, forms, and steps as properties of the space, reads the members of project roles to decide who sees a banner, and reads the screens of a project to check which fields a form can use.
manage:jira-configuration
Feature Bundle reads screens and screen schemes to check which fields the edit screen of a request allows, and checks which workflows a request type uses for forms on a workflow transition. It also reads the list of roles and application properties of Jira. The app doesn’t create or change workflows, screens, or request types.
read:cmdb-object:jira
Feature Bundle searches Jira Assets objects with AQL to show assets in the My assets object and in Assets fields, and to check AQL queries in the configuration.
read:cmdb-schema:jira
When you configure an Assets field, Feature Bundle reads the list of object schemas of Jira Assets for the schema picker.
read:cmdb-attribute:jira
When you configure an Assets field, Feature Bundle reads the attributes of the object schema for the attribute picker.
read:customer.detail-field:jira-service-management
The Attributes object reads which customer detail fields exist, so you can pick them in the configuration.
read:organization.detail-field:jira-service-management
The Attributes object reads which organization detail fields exist, so you can pick them in the configuration.
read:organization.profile:jira-service-management
The Attributes object reads the values of organization details to show them on the request.
read:customer:jira-service-management
The Attributes object reads the customer who reported the request and the name of the customer to show them on the request.
read:customer.detail:jira-service-management
The Attributes object reads the detail values of the customer who reported the request to show them on the request.
Content security: inline styles
The app interface applies styles at runtime, in particular in Announcement Banners, Ticket Journey, Additional Fields, and Customer Actions. For this, the manifest allows inline styles.