Skip to content
Workline
Menu
HelpWhat is stored

What is stored

Workline runs on Atlassian Forge, inside your Atlassian site. It has no servers of its own and makes no request to anything outside Atlassian. The full policy is on the privacy page.

What it asks of Jira

  • read:jira-work: work items with their estimates, dates, sprints and assignees, spaces and saved filters, a booking’s space or work item as the viewer finds it, and the viewer’s own permissions.

  • read:jira-user: Jira’s time tracking settings, a team’s members, the names of the people on screen and Jira’s group list.

  • storage:app: Forge storage, for what is kept below.

  • write:jira-work: used for Move and Apply alone. Move sets a work item’s assignee and, when the person gave one, its due date; Apply, on a plan of unscheduled work, sets a work item’s start and due dates. Nothing else is written, and nothing until someone presses one of them.

It reads and moves as the person using it, so a person sees only the work items their Jira permissions let them browse, and Move and Apply work only where Jira lets them edit the work item. Jira’s history names that person.

What it keeps

  • Settings, one entry per site: the working week, people’s own hours and working days, the holidays, each person’s time off, the groups offered as teams, the roles and who has which, and story points a week for the site and for people.
  • Bookings, one entry each: who it is for (an account id, or a placeholder), what for (the booker’s own words, up to 100 characters, or the key of a space, an epic or a work item, and for a work item or epic its space), the first and last day, the amount (a share, or hours a week), whether it is tentative, who booked it and when, and who changed it last and when. At most 2,000 on a site.
  • Placeholders, one entry each: a role name of up to 100 characters, its first day, its own hours a day and working days if given, a team if picked, and a role if given. At most 200 on a site.
  • Each person’s remembered scope, under their account id: spaces, a saved filter or a JQL search. Kept 90 days from its last change, then Forge storage deletes it.
  • A ten-minute cache of a plan, the hours per person and week, without names.
  • The review request once the app is listed: a person’s account id, how many times they opened the app, counted up to five, and whether they dismissed the banner.

It never stores a work item’s summary, description or fields, nor a space’s name, and the plan itself is never stored: it is worked out again from Jira. A booking’s words are the booker’s own: nobody should put personal data in them.

How long

Settings, bookings and placeholders until the app is uninstalled or someone changes or deletes them. Then Atlassian keeps its storage for 28 days and deletes it.

Where it goes

Nowhere. There is no network request to anything outside Atlassian, and no tracking. Atlassian counts how often each part of the app is used, as a number under a name, with no work item data and no person.