Permissions and data

Logline is a read-only app built on Atlassian Forge. It has no servers of its own and sends nothing outside Atlassian.

Permissions

Logline asks for three:

• read:jira-work: to read issues, worklogs, fields, spaces, saved filters and the viewer’s own permissions;
• read:jira-user: to read the people and Jira groups a report is limited to;
• storage:app: to keep saved reports, settings and the short-lived report snapshots in Forge storage.

It has no write permission. It cannot create, change or delete a worklog, an issue or a setting in Jira.

Whose permissions

Logline reads Jira as the person using it, so nobody sees a worklog, an issue or a comment they could not see in Jira, including worklogs restricted to a group or role. A worklog the viewer may not see is never read and never counted. Two people opening the same shared report can therefore see different totals, and every shared report says so.

What it stores

Everything is in Forge storage, hosted by Atlassian:

• the site’s settings, one entry per site;
• saved reports: name, owner, sharing, scope, people, period and layout, one entry per report, until its owner or a Jira admin deletes it;
• when each person last opened each report;
• report snapshots: the worklogs of one report as one person saw them, comments included (cut to 1,000 characters), served for at most 10 minutes and deleted by Forge storage a minute after that. A big report being read in steps keeps its partial state the same way. One person’s snapshot is never served to anyone else.

Snapshots expire 11 minutes after they are built; saved reports and settings stay until deleted or the app is uninstalled, when Atlassian removes all of the app’s storage.

What leaves your site

Nothing. Logline makes no request to any service outside Atlassian, loads nothing from a CDN, and has no analytics or tracking. Export files are built in your browser. Its logs carry no issue content, keys, comments or account ids.

The full policy is on the privacy page.