Why each permission is needed

• Read Jira work: show requests, fields, statuses and history.
• Write Jira work: mark items done, post comments, change status and set fields. RequestOps does this only after a Jira admin turns a feature on, or when a person selects a button.
• Read Jira users: show names, and find who is away or can cover.
• Service desk requests: show the portal view and ask the customer.
• Data saved on requests and profiles: keep checklist progress on each request, and personal choices on your Jira profile.
• Your own preferences: save your tour and what is new. Saved views and personal replies use app storage restricted to your account; older copies in Jira may remain until separately cleaned up.
• Where preferences live: personal choices are kept in your Jira profile or app storage. Access follows Jira permissions and app checks. Jira admins can export supported app-stored preferences in Privacy and data.
• Approvals: record your decision on a request when you approve from the request panel.
• Settings saved by RequestOps: keep the settings that Jira admins choose.
• Automatic messages: show the app's name in Jira, never a person's name.

What you should see

You can connect each permission to its purpose in the product.

If something is not right

An action is denied. Check Jira permissions for its request and the action’s setup. App installation does not grant every user access.