StatusBeacon for Jira Service Management runs entirely on Atlassian Forge. It has no remote back end and makes no calls outside your Atlassian site.
The app calls three Jira endpoints, all as the agent who's using the Status page. GET /rest/api/3/mypermissions checks whether that person is an agent or a project admin in the project. GET /rest/servicedeskapi/servicedesk finds the service desk that belongs to the project. GET /rest/servicedeskapi/servicedesk/{id}/requesttype gives the id of that service desk's customer portal, and the app keeps only that id. Portal views, which customers see, make no Jira calls.
Data stays in Forge app storage on Atlassian's platform.
| Record | Contents | Kept for |
|---|---|---|
| Status record, one per customer portal | Component names, descriptions and statuses, incident and maintenance titles, update text, states and times, a log of component status changes, three on/off settings | Open items until closed. Closed items and status changes for 90 days |
| Portal copy, one per customer portal | The same record without the change log, holding only the 20 most recent closed items. Portal views read this | Replaced on every save |
| Project link cache | The service desk id, project key and portal id for a project id | 1 day. A failed lookup isn't stored |
The app doesn't store account IDs, names, email addresses or avatars, and it doesn't record which agent made a change. It does store whatever agents type into titles, descriptions and updates, and all of that is shown to portal customers. Agents shouldn't type personal data there.
It has no scope that writes to Jira. It doesn't send data to the developer or to any third party, and it doesn't use analytics or tracking.
Agents can delete any incident from the Status page. Closed incidents older than 90 days are hidden everywhere and deleted from storage the next time an agent saves a change. Forge app storage is tied to the installation, and Atlassian removes it after the app is uninstalled.