Dashboard Notes for Jira, version 1.0.0.
All data sits in Forge storage (KVS) for your site, on Atlassian's cloud.
| Data | Why | Kept for |
|---|---|---|
| Note text, per gadget | To show the note | Until an editor changes it, or the app is uninstalled |
| Up to 10 earlier versions of the note | So editors can restore them | Until 10 newer versions replace them |
| Settings (extra editors, three on/off options) | Per-gadget permissions and display | Until changed |
| Atlassian account IDs of the last editor, version authors and extra editors | To show who edited and to check edit rights | As long as the record above. IDs of closed accounts are removed by a weekly job |
The app doesn't store names, emails or avatars. Jira shows those from the account ID when the gadget loads.
The extra-editor list is sent only to the dashboard owner and Jira admins. When "Show who edited the note last" is off, people who can't edit the note don't receive the last editor's account ID or the edit time.
As the signed-in user, it reads the dashboard (to learn whether the user can see it and who owns it) and the user's "Administer Jira" permission. It doesn't read work items, comments or projects.
Nothing. The app has no external fetch permissions and no remote backend.
A weekly scheduled job sends the stored account IDs to Atlassian's personal data reporting API, at most 90 per request. Each run reads up to 2,000 stored records and the next run picks up where it stopped. Account IDs that Atlassian reports as closed are removed from notes, versions and editor lists.
Use the support link on the Marketplace listing.