What is stored
Changeline reads Jira as the person using it and writes nothing to Jira. It has no servers of its own: it runs on Atlassian Forge and stores what it keeps in Forge storage, inside the Atlassian cloud. Nothing leaves your Atlassian site.
What it asks of Jira
Two permissions, and no others.
read:jira-work: to read spaces, versions, work items with their dates, status changes, links, affected versions, fix versions and priority, work types and statuses, saved filters, and the viewer’s own permissions.storage:app: to keep its settings, its cache and each person’s remembered scope in Forge storage.
There is no permission to read users and none to write to Jira. No figure names a person. The one name Changeline reads is each saved filter’s owner’s display name, shown only to tell apart two filters with one name and never stored.
What it stores
- The settings a Jira admin chooses, one entry for the site: whether a deployment is a released version or a work item reaching Done, when lead time starts, the failure work types and the spaces failures are also read from.
- An hour’s cache of the answer, the figures and the rows they were counted from, kept per person, scope and period, so a page opens at once. Each figure is set against the same number of days just before the period, so the answer holds both periods’ rows. The rows hold the keys and titles of the work items the figures count, with the work types, statuses and dates their tabs show. After an hour, or when someone presses Recalculate, it is read from Jira again.
- Ten minutes’ cache of a work item, for the work item panel and the Details column, kept per person and work item. It holds that work item’s key, title, space and dates, the release it shipped in by name, the keys of the work items that point at that release as failures, and, for a failure, what it points at. No person’s name. After ten minutes, or when someone presses Recalculate, it is read from Jira again.
- The scope a person last showed: spaces, a saved filter’s id and name, or a JQL search they wrote. It is kept for 90 days from its last change, then Forge storage deletes it.
- The site’s work types, their ids, names and levels, kept for an hour for the whole site, so the app does not ask Jira for them on every page. They name no person.
- The “where Changeline shows up” card: for each person who dismissed it, their account id and the date, so it stays dismissed. Kept until uninstall.
- The review request: once Changeline is listed, each person’s account id, how many times they opened it, counted up to five, and whether they dismissed the banner.
Nothing else is kept: the figures are worked out again from Jira each time a cache runs out.
Where data goes
Nowhere. Changeline makes no requests outside Atlassian, loads nothing from a CDN, uses no analytics service and shares nothing with third parties. Atlassian counts how often each part of the app is used on your site, and shows us those counts: a count is a number under a name, with no work item data and no person.
When it is uninstalled
Atlassian keeps the app’s storage for 28 days after it is uninstalled, then deletes it. A reinstall starts empty. Changeline holds no copy of your data, so there is nothing for us to return or delete on request.