See who has time, week by week.

Each person’s planned hours against the hours they can work. Book time with no estimate, plan a hire, move work to who has room.

Space tab
Apps page
Work item panel
Dashboard gadget

Inside Jira. Privacy first. No servers. It changes Jira only when you press Move or Apply.

Workline’s tab in a Jira space: one row per person, one column per week.

Plan it in Jira

Estimate it, date it, give it to someone. Workline plans the rest, with nothing to set up.

Set an estimate
Fill in Original estimate on the work item.
Set its dates
Add a Start date and a Due date, or put it in a sprint.
Assign it
Choose who does the work.
See it on the work item
Workline shows its hours and the assignee’s week right in its Details, and who has room.

Getting started, step by step →

Every space, one plan

A person’s work in every space you pick lands in one row, so each week shows what they carry in all of it. Look at everyone, at a team, at the people who are over capacity, or by epic or by role.

Apps › Workline over the Customer Portal and Portal mobile app spaces, everyone: a row per person, nine people and a placeholder, and a column per week, each week’s planned hours from both spaces with the share of the hours that person can work as a lozenge, Ada Isadora in red in the week of 9 Nov, Emma Paris in red in the week of 16 Nov and Alana Grant with work in her week off, then Total and Unscheduled. — Everyone: each person’s weeks across Portal and Mobile app.

Apps › Workline over the Customer Portal and Portal mobile app spaces with the team Portal Squad picked: a row for each of the seven members of the group, each week’s planned hours from both spaces with the share as a lozenge, Ada Isadora in red in the week of 9 Nov and Emma Paris in red in the week of 16 Nov. — A team: the members of a Jira group, each with their weeks across both spaces.

Apps › Workline over the Customer Portal and Portal mobile app spaces with Over capacity picked: only the three people over in at least one week, Ada Isadora and Emma Paris in red and Alana Grant with 10h planned in her week off, each week’s planned hours from both spaces with the share as a lozenge. — Over capacity: only the people who are over in at least one week.

Apps › Workline over the Customer Portal and Portal mobile app spaces with Rows set to Epic: a row per epic of both spaces, each with its key and name and how many work items it holds, and a column per week with the hours its open work items need that week, no lozenge, and a row for booked time outside any epic, then Total and Unscheduled. — By epic: the hours each epic needs, week by week, with the work items under it.

Apps › Workline over the Customer Portal and Portal mobile app spaces with Rows set to Role: Developer with 5 people, Designer with 2, QA with 1 and No role with 2, each week its people’s hours against the hours they can work as a lozenge, Designer at 89% in 16–22 Nov, then Total and Unscheduled. — By role: each role’s hours against the hours its people can work.

Did the plan hold?

Add the last two or four weeks to the plan: the hours each person logged, or the story points they finished, against what they could work. Teams that estimate in story points can plan in them too.

Planned vs doneStory points

Apps › Workline over the Customer Portal and Portal mobile app spaces with Weeks back set to 4 weeks and four weeks ahead: four past columns headed Logged, each person’s hours logged that week against the hours they could work as a lozenge, mostly 50% to 100%, then This week and the weeks ahead with the hours planned, Ada Isadora at 130% in 9–15 Nov and Emma Paris at 140% in 16–22 Nov, each person’s role in grey under their name, then Total and Unscheduled. — Weeks back 4: what each person logged in the last four weeks, then the weeks ahead, each against the hours they could work.

Apps › Workline over the Customer Portal and Portal mobile app spaces with Unit set to Story points: each week’s story points planned for each person against their own pace, the points they finished a week over the last six weeks, as a lozenge, Ada Isadora at 116% in 9–15 Nov and Emma Paris at 207% in 16–22 Nov, then Total and Unscheduled in points, and a grey line above the table saying how the pace is worked out. — Unit Story points: the points planned each week against what each person does in a week, from their own pace.

On the work item

A work item shows its assignee’s week with and without it, what fills that week, and who has room, each with a Move. When they are over capacity it says so.

Workline’s panel on PORTAL-5 Return label PDF: a grey first line with Ada Isadora, her week of 9–15 Nov and Recalculate, rows with bars for this work item, Ada’s week at 52h of 40h in red and the week without it at 28h, an amber box saying Ada Isadora is over capacity in 9–15 Nov, a table of what fills her week, a Who has room table with each person’s hours that week and with PORTAL-5 and a Move on each, and a link to open Workline. — The Workline panel on a work item: the assignee’s week, what fills it, and who has room.

Book time that has no estimate

Set aside part of a person’s time for onboarding, support or a space, an epic or a work item. On a work item or an epic it counts the larger of the booking and the estimated work in it, never both. Not sure yet? Mark it tentative, and leave tentative time out when you want the sure plan.

A person’s row opened in the Workline plan: their work items listed under their name, each with its planned hours in each week and in total and the one with no dates in the Unscheduled column, then their Onboarding booking and Open in Logline. — A person opened under Apps › Workline, with a booking under their work items.

Put work where there is room

Over capacity? Press Move on a work item: everyone’s load is shown before and after, and Jira reassigns it as you. Work with no dates? Press the hours under Unscheduled: Workline suggests start and due dates in the earliest days that person has room, highest priority first. Change any, then Apply.

MovePlan unscheduled work

The Move dialog for one work item: its remaining hours and weeks on a grey line, then every other person on the plan with their hours in those weeks before and after, as a lozenge, the lightest first, a Pick button on each, a New due date field, and Move and Cancel. — The Move dialog: each person’s hours in its weeks, before and after.

The Plan unscheduled work dialog for Ada Isadora: a grey line saying each work item takes the earliest days its assignee has room, highest priority first, then PORTAL-17 Password breach check, ticked, 14h remaining, with a suggested Start date of 3 Nov 2026 and Due date of 5 Nov 2026 you can change, a grey line saying it fills Ada Isadora’s days, 3–5 Nov, at her 8h a day, and Cancel and Apply. — Plan unscheduled work: each work item with no dates, with the start and due dates Workline suggests, before Apply.

The next four weeks, on a dashboard

Each person’s next four weeks, over capacity first, on any Jira dashboard. Each viewer counts only the work items they may browse.

The Workline gadget on a dashboard: a grey first line counting the people over capacity, then a table of each person’s next four weeks with their share of capacity as lozenges, over capacity first, and an Open in Workline link. — The Workline gadget, added to a dashboard like any other.

How the hours are worked out

Remaining estimates of open work items
Or the original estimate less what was logged, when Jira has no remaining one.
Spread over the dates it has
Its 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.
Against the hours a person can work
Jira’s time tracking settings or Workline’s own, part-time hours, holidays and time off.
As a share, week by week
Green to 100%, yellow to 120%, red past it. A Total for the weeks shown.

What it never guesses

No dates, no week
A work item with neither dates nor a sprint is shown as Unscheduled, never put in a week.
Late work is flagged
A work item past its due date or sprint end is planned for today, and marked Late.
A parent’s estimate counts once
When a parent and its children both have a remaining estimate, the children’s count, and the parent’s own value is named.
Story points need a pace
A person’s points a week is what they finished in the last 6 weeks, or the number a Jira admin sets. With neither, their points show with no lozenge.
A booking counts once
A booking on a space, an epic or a work item counts the larger of it and the estimated work in it, week by week, never both.
Jira changes only when you press Move or Apply
Move sets the assignee and, if you give one, the due date. Apply, on a plan of unscheduled work, sets the start and due dates you left ticked. Both as you. Never an estimate, never anything else.

What you get

The plan

One row per person, one column per week: 4, 8, 12 or 26 weeks, each week’s planned hours against the hours they can work.
The share as a lozenge: Green to 100%, yellow to 120%, red past it.
A person’s work items: Open a row to see each work item with its hours in each week.
Weeks back: Add the last 2 or 4 weeks: the hours each person logged, or the points they finished, against what they could work.
Story points: Plan in points where your work items carry them, against each person’s own pace.
Rows by role, epic or space: A role’s hours against its people’s capacity, or the hours an epic or a space needs, week by week.
Total and Unscheduled: The weeks’ total, and the hours on work items with no dates and no sprint.
Open in Logline: Each opened person links to the hours they logged, in Logline.

Plan ahead

Book time: Part of a person’s time, as a share or hours a week, with no estimate behind it.
Tentative bookings: Mark a booking tentative, then count it or leave it out with one switch.
Plan unscheduled work: Suggested start and due dates in the earliest days each person has room, highest priority first. Edit, then Apply.
Counted once: On a space, an epic or a work item, the larger of the booking and the estimated work in it.
Placeholders: A row for a hire you have not made. Fill it with a person and its bookings move over.
Move work: Give a work item to someone with room, seeing everyone’s load after. Jira reassigns it as you.

The hours people can work

Jira’s time tracking, by default: Its hours a day and days a week. Or Workline’s own.
Part-time: A person’s own hours a day and working days.
Holidays and time off: Days nobody works, and the days one person does not.

Across your site

Teams: Jira groups a Jira admin offers. A team’s members each get a row, with or without work.
Filters: Team, Weeks, Space, People, Role and Over capacity, then Book time and Placeholder.
Who is over, who is free: The people over capacity, and the people with time free.
Excel, CSV and a link: Download the plan, or copy a link with every choice in the address.
Dashboard gadget: Each person’s next four weeks, over capacity first.

For Jira admins

Workline settings: The working week, part-time hours, holidays, time off, the groups offered as teams, roles and story points a week.
Roles and points a week: Name the roles and give each person one. Set a person’s story points a week, or the site’s.
Who can book: Everyone who can open Workline, or only the groups you choose.
Kept on Atlassian: Its settings, bookings and placeholders, account ids, each person’s remembered scope and a ten-minute cache of a plan without names.

Dark mode, too

Every Lineset app follows your Jira theme, light or dark.

Workline’s tab in the Customer Portal space in Jira’s dark theme, on a dark background: the space’s header and tabs, the counts and filters, then the plan, a row per person and a column per week with the share lozenges and one person over capacity in red.

Secure and private

Inside Jira: It runs where your Jira runs, and nothing leaves your site.
No servers: None of ours, and no external services: nothing is sent anywhere.
One write: The assignee and due date on Move, and the start and due dates on Apply when you plan unscheduled work, as you.
Reads as you: Your own Jira permissions apply to what it reads.

Built on Atlassian Forge. No tracking. What it reads and stores →

Pricing

Free up to 10 users

The price per user drops as you grow

Billed by Atlassian
Every feature on the free tier
30-day free trial

Get notified

Questions

What does it show right after I install it?

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.

Does Workline change my work items?

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.

Is it fast?

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.

What about work with no dates?

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.

What does it cost?

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.

All questions →Doing it with Jira’s own tools? Step-by-step guides →

Works well with

LoglineWho logged the hours, on what