...
Scope | Why we need it |
|---|---|
storage:app | Required for storing created reminders and app configuration. |
read:jira-work | Required for reading issue status and resolution fields. Also required when sending reminders to "Reporter", "Assignee" to check whether these fields has any values. |
write:jira-work | Required for sending notification e-mails using Jira's build-in e-mail API and adding adding issue comment about the reminder if this option is enabled. |
read:jira-user | Required for converting from Account IDs to actual user information such as username, display name. |
manage:jira-configuration | Required for determining Jira Server's and user's locale for internalization. |
Access to rem.thestarware.com | We use this server for authenticating with Slack and periodically asking Forge platform to send pending reminders. In other words, you reminders doesn’t go to rem.thestarware.com, but the rem.starware.com periodically pings your instance for sending remindersfor our legacy Slack integration. We have a new way of sending messages to Slack using hooks which don’t require authentication credentials. We will remove our old Slack integration at the end of 2025. |
Access to slack.com, azure.com and google.com | We are using slack, MS Teams and google APIs to send reminders to Slack, MS Tems and Google Chat. If you don’t enable these services we don’t send any data to their API. |
...