Questions

No. Inside Jira, no servers. Workline runs on Atlassian Forge and reads Jira as you. The only things it writes to Jira are a work item’s assignee and due date when you press Move, and its start and due dates when you press Apply on a plan of unscheduled work. Nothing is sent anywhere.

Not yet: Workline is not on the Atlassian Marketplace. Leave your email for one message the day it is live.

A plan. Workline reads the estimates, dates and sprints your work items already have, so the first page it opens is the plan, with nothing to set up first. Jira’s time tracking settings give the hours a day and days a week until you set Workline’s own.

Only when you press Move (the assignee and, if you give one, the due date) or Apply on a plan of unscheduled work (its start and due dates). It does it as you, with your Jira permissions, so Jira’s history names you. Bookings and placeholders are kept in Workline’s own storage, never on a work item.

In our test it read a whole demo site’s 70 open work items in under 3 seconds. A plan is kept for ten minutes, without names, and Recalculate reads it again.

The plan is built from the work items you already estimate and date, so there is no second list to keep. Part-time hours, holidays and time off are set once in Workline settings. Download the plan as Excel or CSV when someone wants it in a sheet.

Free up to 10 users, then billed per user by Atlassian, with a 30-day free trial. Every feature is on the free tier. The price per user drops as you grow, and the Marketplace listing shows the exact cost for your site.

From the remaining estimates of open work items, or the original estimate less what was logged when Jira has no remaining one. They are spread over each work item’s start and due dates, else its sprint’s dates, from today on. A start date alone is worked at the person’s own hours a day.

It is shown as Unscheduled, with its hours, and is never guessed into a week. Add a due date or put it in a sprint and it moves into the weeks it falls in. Or press its hours under Unscheduled and Workline suggests dates.

Yes, when you ask it to. Press a person’s hours under Unscheduled and Workline suggests a start and a due date for each of their work items with none, in the earliest days they have room, highest priority first. Untick any or change a date, then press Apply. Workline writes the dates to Jira as you, so Jira’s permissions decide and its history names you. Nothing is written before Apply.

It is planned for today and marked Late, so the work still counts and you can see it is behind. The same goes for a work item whose sprint has ended.

No. When a parent and its children both carry a remaining estimate, the children’s count and the parent’s own value is named, so you can see what was left out.

Yes. A Jira admin sets each person’s own hours a day and working days, the holidays that count as no hours for everyone, and a person’s time off. A week with no working hours shows Off.

Yes. A Jira admin offers Jira groups as teams in the settings. Pick one with the Team filter and every member gets a row, with or without work.

Yes, where your work items carry story points. The Unit chip switches the plan from Hours to Story points: points are spread over each work item’s dates as hours are, against what each person does in a week. That is their own pace, the points they finished in the last 6 weeks, or a number of points a week a Jira admin sets. With neither, their points show with no lozenge, and a grey line says so.

Yes. Weeks back adds the last 2 or 4 weeks before this one: the hours each person logged, or in story points the points they finished, against what they could work. This week shows what was logged so far under what is planned. Open a person to see the work items behind it. The Total, Unscheduled and the counts stay the planned weeks.

Yes. Book part of their time: a share of each working day, or hours a week, for the days you pick, with no estimate behind it. Say what it is for in your own words, or by the key of a space, an epic or a work item. Where it is on a space, an epic or a work item, it counts the larger of the booking and the estimated work in it, never both. Mark a booking tentative and the Include tentative switch counts it or leaves it out.

Yes. Add a placeholder: a row for a role, such as Backend developer, with its first day and its hours. Book it on a space, an epic or a work item. When you hire, fill it with the person and every booking moves onto them.

Yes. Press Move on a work item under someone over capacity. The dialog lists everyone on the plan with their hours in that work item’s weeks before and after, the lightest first. Pick one, add a new due date if you like, and Jira reassigns it as you.

Jira administrators change the settings, under Jira settings › Apps › Workline settings. Everyone who can open Workline can book time and add placeholders, until an admin narrows it to chosen groups there. Everyone else sees the plan of the work items they may browse.

Its settings, the bookings and placeholders, account ids, each person’s remembered scope, and a ten-minute cache of a plan without names. It never stores a work item’s summary, description or fields. It writes to Jira only when you press Move (the assignee and due date) or Apply (start and due dates).

Work items with their estimates, dates and sprints (read:jira-work), people’s names and groups (read:jira-user), and its own storage (storage:app). The one permission that writes (write:jira-work) is used for Move and for Apply on a plan of unscheduled work alone, as the person pressing it, so their Jira permissions apply to what it reads and to what it changes.

Ask support first: it may already be a setting. If it is another app, tell us. When other teams need it too, we build it.

Request an app →