Skip to content
Menu
HelpPrivacy, permissions and data

Privacy, permissions and data

No servers. Changes nothing in Jira. Logline reads your worklogs and work items as you, writes nothing back, and runs on Atlassian Forge with no servers of its own.

Permissions

Logline asks for three:

  • read:jira-work: to read work items, 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, a work item or a setting in Jira.

Whose permissions

Logline reads Jira as the person using it, so nobody sees a worklog, a work item 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.

A Jira admin can also keep everyone’s worklogs to chosen Jira groups in Logline settings: everyone else then sees only their own worklogs in Logline, or cannot open it. Logline enforces that itself, for every report, the dashboard gadget and the work item panel, whatever a page asks for.

Cost, margin and budgets

Cost and margin are for the members of one Jira group the admin picks, and for nobody while none is picked: a Jira admin sees them only as a member, as the admin sets the rates and need not see what people cost. Logline asks Jira, as the person, whether they are in it, at most once an hour, and sends the cost rates to a page only when the answer is yes, so a downloaded file never holds a cost or margin the person could not see on screen. Budgets are shown only to people who see everyone’s worklogs, since their spent figures count everyone’s time. See Set a budget and See cost and margin.

Worklogs hidden from you

Jira’s own time spent on a work item counts every worklog on it, also those restricted to a group or role you are not in. When Logline holds every worklog you may see on a work item, it compares the two, and a report with a difference says so under its totals: “3h on 1 work item is in worklogs hidden from you”. That time is never added to the report, and it may have been logged on any date, not only in the report’s period.

Logline can only check a work item whose worklogs all came with it when it was read: up to 20 that you may see. A work item with more is read for the report’s period only, so its hidden time, if any, is not in the line.

What it stores

Everything is in Forge storage, hosted by Atlassian:

  • the site’s settings, one entry per site, the Jira groups an admin chose by id and name among them; the cost rates and the one Jira group that sees cost and margin, and the budgets with the client field, each in an entry of its own;
  • saved reports: name, description, owner, sharing, editors, scope, people, period and layout, one entry per report, until its owner or a Jira admin deletes it. People are kept by account id, never by name;
  • when each person last opened each report, and which reports each person starred as favourites (at most 100, by report id);
  • report snapshots: the worklogs of one report as one person saw them, comments included (cut to 1,000 characters), each author by account id, served for at most 10 minutes and deleted by Forge storage about 11 minutes after it is written; the work item panel keeps its read of one work item and its children, summaries and comments included, the same way. A big report being read in steps keeps its partial state the same way, and so does the list of spaces and saved filters the report builder offers you. One person’s snapshot is never served to anyone else;
  • what a report’s whole-work budgets count: the worklogs of the budgeted spaces and clients, with no comments, and each budgeted epic’s totals (hours, amounts and the work item keys whose estimates were left out), under the person’s account id, served for at most an hour and deleted by Forge storage about 61 minutes after it is written;
  • when an admin keeps everyone’s worklogs to chosen Jira groups, whether each person may see other people’s worklogs, worked out from their Jira groups (the groups themselves are not kept), kept for an hour under their account id;
  • the site’s field list, shared by everyone on the site and deleted by Forge storage about an hour after it is written. It names no person.
  • for each person who dismissed the “where Logline shows up” card (on the Apps page and the settings page), their account id and when, so it stays dismissed, until the app is uninstalled;
  • once Logline is on the Marketplace, for each person, their account id, how many times they opened Logline, counted up to ten, and when they dismissed the banner: from the tenth open, Review Logline ⭐, a link to its reviews, shows on the settings page, and in a banner at the top of the space page and the Apps page until dismissed. Kept until the app is uninstalled.

People are kept by account id only. Names and time zones come from Jira while a report is open, and none is stored.

Snapshots are deleted about 11 minutes after they are built, what whole-work budgets count about 61 minutes after (Forge clears expired entries in the background, within 48 hours). Saved reports and settings stay until deleted, and each person’s last-opened times, for their 200 most recent reports, stay too, as do their favourites until they unstar them; a star on a report deleted or no longer shared with them is dropped the next time they open Saved reports. When the app is uninstalled, Atlassian keeps its storage for 28 days, then deletes all of it. A reinstall starts empty: the old storage, saved reports included, comes back only if you ask us within 21 days of uninstalling.

What leaves your site

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

Atlassian counts how often each part of Logline is used on your site and shows us the counts. A count carries no work item data and names no person.

The full policy is on the privacy page.