Skip to content
Menu

Jira worklog reports, ready to bill.

Timesheets by client, epic or person, from Jira’s own worklogs. No approvals, no new fields.

Privacy first. No servers. Changes nothing in Jira.

Jira’s Spaces header and the Acme Website space with its Logline tab picked among Summary, Reports, List and more, the page headed Logline: Whose time Everyone, Period 1 Sep – 30 Sep with its arrows, Show report, and Save, Reports, Copy link and Download at the right; one grey line, “1 Sep – 30 Sep · 147 worklogs · Counted in America/New_York”, with Recalculate; then the Timesheet by epic, then work item, Per Total only, sorted by Margin, ascending, with Total, Billable, Amount, Cost and Margin, then Budget, Spent, Left, % used and At completion. The Total row reads 302h 45m, 270h 30m billable at 89%, USD 40,575.00, USD 12,110.00 cost and USD 28,465.00 margin. ACME-1 Q4 storefront has 223h 45m of a 300h monthly budget, 76h 15m left, 75% used, USD 20,300.00 margin. Its first work item, the lowest margin, is ACME-7 Order history page: 19h with nothing billed, USD 760.00 cost, a margin of −USD 760.00, opened to its nine worklogs by Mitch Davis and Alana Grant, each with its date, hours and comment; then ACME-8 Discount codes at −USD 390.00, and the billed work items up to ACME-3 Payment form, USD 8,140.00. Then No epic, 79h.
Acme Website’s own Logline tab, the lowest margin first: the work no one is billing for leads, down to every worklog.

Log time in Jira

Log with Jira’s own Log work and Logline reads it: no timer, no separate timesheet app.

  1. Set an estimate

    Fill in Original estimate in the work item’s Details.

    Jira’s Details panel on a work item: Original estimate 1d, then Time tracking with a bar, 3h logged on the left and 5h remaining on the right.
  2. Choose Log work

    Open More actions on the work item, then select Log work.

    Jira’s More actions menu, three dots at the top right of a work item, open: Log work is the first item, then Open command palette and Add flag, and the menu goes on.
  3. Add the time

    Add the time spent and what you did. Jira works out the time remaining itself.

    The Time tracking dialog that Log work opens: a bar showing 3h 30m logged and 4h 30m remaining, the original estimate 1d, Time spent 30m, Time remaining 4h 30m, Date started with a date and a time, a Work description reading Reviewed the checkout copy, and the Save and Cancel buttons.
  4. See it in Jira

    Logline shows the hours inside Jira, with nothing to set up.

    Logline’s part of an epic’s Details column: Original estimate 542h, Logged 470h 30m with “last 6 Oct” beside it, and Remaining 184h with their bars on one scale, the remaining running red past the estimate, Billable 456h 30m at 97% and, under it, “at end 497h 15m” at 76%, an amber “Ends with 157h 15m not billable:” line naming HLAB-5 109h 15m, HLAB-3 42h and HLAB-2 6h, an amber “Over estimate:” line with their percents (HLAB-5 158%, HLAB-2 150% and HLAB-3 135%), and “Updated 6 min ago · Recalculate” as its last line, at the bottom left, with no facts line above the rows

Log time, step by step →

By client, epic or person

Pick the rows and the month regroups by client, epic, person or work type, down to each worklog, with billable hours and their amount beside each total.

The same page over Harbor Labs with Rows set to Person, a column per week, the estimate columns and Sort: Remaining %, Descending: the Total row, 704h 30m, then Cassi Owens, 170h 30m, “3 over”, open on the work items furthest over first, HLAB-5 Product page SEO with a red 158% remaining, HLAB-2 Checkout redesign at 150%, opened to its two worklogs, each under its week, and HLAB-3 Payment form at 135%; then Mitch Davis 178h 30m, Alana Grant 176h 45m and Kevin Campbell 178h 45m, closed, each with their picture and a billable share.
Rows by person, a column per week: each person’s month, the work items it went on and their worklogs.
The Logline page under Apps, from its heading, over four spaces and everyone’s time: the scope row, the report on 1 to 30 September with “929 worklogs” on its facts line, the Timesheet and Worklogs tabs and a row of chips with Rows: Space, Then by: Work item, Per: Week and Sort: Remaining %, Descending. Columns: Total, Billable, Amount, a column per week from the part week 1–6 Sep to the part week 28–30 Sep, then Original estimate, Logged (all time) and Remaining. The Total row first, 1357h 15m, 927h 15m billable at 68%, USD 56,655.00; then Harbor Labs, 704h 30m, “3 over”, open on its work items furthest over first: HLAB-5 Product page SEO with a red 158% remaining, HLAB-2 Checkout redesign, 14h logged against 12h, a yellow 117%, and a red 150% remaining, opened to its five worklogs by Mitch Davis and Cassi Owens, each under its week, and HLAB-3 Payment form at 135%, down to three work items with no estimate; then Acme Website 302h 45m, “2 over”, USD 40,575.00, Internal 118h 15m and Northwind App 231h 45m, closed.
Rows by space, a column per week: each space’s hours, amount and estimates, down to each worklog.
The same page with Rows set to Epic, a column per week, the estimate columns and Sort: Remaining %, Descending: the Total row, 1357h 15m, then HLAB-1 Q4 storefront, 275h 45m, “3 over”, open on its four work items furthest over first, HLAB-5 Product page SEO with a red 158% remaining, HLAB-2 Checkout redesign at 150%, opened to its five worklogs, each under its week, HLAB-3 Payment form at 135% and HLAB-4 Card validation; then ACME-1 Q4 storefront 223h 45m, “2 over”, HLAB-7 Mobile app v2 150h 15m, NWND-1 Mobile app v2 162h 30m and 545h on work items with no epic, closed.
Rows by epic, a column per week: what each epic took across spaces, down to each worklog.
The same page with Rows set to Work type, a column per week, the estimate columns and Sort: Remaining %, Descending: the Total row, 1357h 15m, then Story, 631h 30m, “5 over”, open on its stories across the four spaces furthest over first, HLAB-5 Product page SEO with a red 158% remaining, HLAB-2 at 150% and HLAB-3 at 135% down to NWND-5 Dark mode, with ACME-8 Discount codes opened to its six worklogs, each under its week; then Bug 180h 45m, Sub-task 64h 30m and Task 480h 30m with a red 23% billable, closed.
Rows by work type, a column per week: stories, tasks, bugs and subtasks, a bug opened to its worklogs.

Ready to send with the invoice

A client’s billable hours as a timesheet PDF for the invoice, or a file Xero or QuickBooks imports. Logline sends nothing itself.

The top of the timesheet PDF Logline downloads: the period as its title, 1 Sep – 30 Sep, the Jira site and when it was downloaded; Billable hours 404h 30m, the rates and the amount; then the work items under Acme Website and Northwind App with hours, rate and amount, and the Total row.
The timesheet PDF for one client and one month: the billable hours, the rate and the amount, then each work item.

Save it, share it, send the link

Save a report and share it with people, Jira groups or the whole site. Each viewer sees only the worklogs Jira lets them see.

The Share report dialog over a saved report: Only me, Chosen people, Jira groups, and Everyone on this site, which is picked; a line saying that people you share with can open the report and save a copy, only you and its editors can change it, and each viewer sees only the worklogs Jira lets them see; Editors, with Cassi Owens added; Cancel and Done.
Share report: everyone on this site can open it, and one editor can change it.

On every work item: logged against the estimate

Who logged it and when, and on which child work item, in the work item’s own panel, with a link that opens it in the report.

The Logline panel on an epic: “4 child work items · last logged 6 Oct” with “Updated 1 min ago · Recalculate” at its right; Original estimate 542h “(from child work items)” over a blue bar, Logged 470h 30m over a green bar, and Remaining 184h “(worked out) · ends 112h 30m over”, its bar green to the estimate and red past it; Billable 456h 30m with a 97% lozenge, then “at end” 497h 15m with a 76% lozenge; three grey lines saying which estimates were left out, which remaining was worked out and which 14h are past the original estimate; an amber box, “Check these work items”, saying the work ends with 157h 15m not billable; then the four child work items with their status, Original estimate, Logged with its work ratio (79%, 117%, 110%, 80%), Remaining with where the work ends (158%, 150% and 135% in red; HLAB-4 closed, its key struck through) and Billable (HLAB-2 at 86%, HLAB-3 at 91%); and Open in Logline as its last line
The Logline panel on a work item: the time against its estimate, by person and by child work item.

Any saved report on a Jira dashboard

A saved report’s total and biggest rows on any Jira dashboard, as each viewer may see them.

A Jira dashboard named Agency overview with one Logline gadget, the saved report Work left: its grey first line “Work left · 1 Sep – 30 Sep · 447 worklogs”, then one line, 652h 45m logged, 404h 30m billable at 62% and USD 56,655, then a row per work item with its status, logged hours, original estimate, logged in all time, remaining, billable and amount, the work furthest over its estimate first: ACME-2 Checkout redesign, 14h against 12h, a yellow 117% and a red 133% where it ends, then ACME-5 Product page SEO at 109%, with Show 9 more under its tenth row and Open in Logline.
The gadget on a dashboard: the work left on each work item, the one furthest over its estimate first.

Every worklog, with its comment

Every worklog in the period with its date, author, work item, hours and comment. Sort it, filter it, download it to Excel or CSV.

The Worklogs tab of a report on September, sorted newest first, with a filter box, Billable only and Columns. Each row has the date and time, the author with their picture, the work item key and summary, the hours, whether it is billable, the rate and amount in USD and the comment, such as Cassi Owens, 1h 30m on MS-7 Launch event page, billable at USD 150 an hour for USD 225: Checked with both clients. MS-8 Team planning is not billable, so it has no rate or amount.
September’s Worklogs tab: every worklog with its comment, newest first.

How it counts

  • A worklog counts on the day it started

    In the viewer’s time zone, or in each author’s. Every report names the zone under its total, “Counted in Europe/Riga”, and How this is counted spells the rule out: “A worklog counts on the day it started, in Europe/Riga.”

  • Totals match Jira to the minute

    Hours are added up in seconds and rounded once, then shown as 7.5h, 7h 30m or 1d 2h.

  • Every worklog counts once in every total

    A worklog under two rows, such as a work item with two labels, counts in each of those rows, and the report says so.

  • You see the worklogs Jira lets you see

    Every read is made as the person viewing, so a shared report’s totals can differ between viewers, and it says so.

What you get

Bill a client

Billable hours and the amount
Hours up to each work item’s original estimate are billable from install; an admin takes out spaces or a label, or marks only client work by space, label, field or JQL, with hourly rates by client, space or person, from a date.
Timesheet PDF
A client’s billable hours, rates and amount for the period, to send with the invoice.
Xero and QuickBooks
The billable lines as the file each one’s invoice import takes, a draft you check before sending.
Budgets, cost and margin
A budget in hours or money per space, epic or client; cost and margin seen only by the Jira group you choose.
Duplicate worklogs caught
With Gaps on, a person’s day with more than 24 hours logged turns red, so a double entry is found before the invoice.

Reports

Opens ready
The last 30 days, by space and work item, with the billable hours and their amount up front, then the report you last had open.
A tab in every space
The same report, limited to that space, with its own saved reports.
On every work item
Time logged against the estimate, by person and by week.
Every worklog, with its comment
Five sorts and a filter by comment, work item or author, with a live count of what is shown and its hours.
Saved and shared
Share a report with people, Jira groups or everyone, and name who may edit it.
On the dashboard
Any saved report’s totals, with a link to the report.
Every saved report, in view
A Jira admin sees every saved report on the site and hands one to a new owner when someone leaves.

Also

Excel and CSV
The worklog list exactly as shown, the timesheet as a flat list a spreadsheet can add up.
Against the estimate
Original estimate, remaining estimate, time spent and work ratio on every work item row.
Gaps and overspend
An empty working day in yellow, a work item’s share of its estimate in green, yellow or red. Off by default.
Rows that open
Every worklog listed under its row, with date, author, hours and comment.
Never a partial total
Up to 10,000 work items and 50,000 worklogs a report; past that, Logline says so.
Admins choose
Time zone, week start, working day, hours format, who may share and who sees whose worklogs.

Rows, columns and periods →

Dark mode, too

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

Logline’s tab in the Acme Website space in Jira’s dark theme, on a dark background: the scope row with Whose time, Period, Show report, Save, Reports, Copy link and Download, the report’s facts line, then hours by epic and work item, the lowest margin first, with Billable, Amount, Cost, Margin and the budget columns on Q4 storefront, and ACME-7 Order history page, −USD 760.00, opened to its worklogs.

Secure and private

Runs on Atlassian
Your data stays on your Atlassian site.
No servers
None of ours, and no outside services: nothing is sent anywhere.
Changes nothing
It reads Jira and writes nothing back.
Reads as you
It sees only what your permissions allow.

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

Questions

We log time in Tempo. Does Logline see those hours?

It sees the hours, but not who logged them. Timesheets by Tempo writes each worklog to Jira under its own app account and replaces the comment with its own text, so in Logline those hours show under Timesheets by Tempo, without the comment. Time logged with Jira’s own Log work shows under the person, as usual. Checked on 7 October 2026 with Tempo’s Forge app.

Our worklog report is a Connect app. Can Logline replace it?

It is built to. Logline runs on Forge and mirrors the views a Connect worklog report offers: a timesheet grouped by a field, a daily, weekly or monthly split, fixed and rolling date ranges, worklogs as rows with their comments, a work ratio column, grouping by Jira group, saved and shared reports, and export to Excel and CSV.

To move, install Logline, rebuild each saved report once (period, rows, columns, people) and share it the way the old one was shared. Both apps can run side by side while you compare totals.

What you used, and where it is in Logline →

Do people have to log time differently?

No. Logline is a reporting-only app over Jira’s native worklogs: no timers, no approvals, no new fields. People keep logging time the way they do today, with Jira’s own Log work or any app that writes Jira worklogs, and Logline reads those worklogs.

How to log time in Jira, step by step →

Does Logline watch what people do?

No. It reads only the worklogs people write in Jira themselves: no timers, no screen capture, nothing recorded while they work. An admin can also show each person only their own worklogs, under Logline settings › Who sees whose worklogs.

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

Works well with

See where the hours went

Install it. Open Logline. The last 30 days are there.

Get it on Atlassian Marketplace