Who logged how many hours on what, in which period, with the worklog comments
One timesheet, read from Jira’s own worklogs. No timers, no approvals, no new fields.
Built on Forge. Your data never leaves your Atlassian site. Read-only: nothing is changed in Jira.
The timesheet you already know
Pick a period, group rows by person, issue, epic, space, priority, component, label, a select field or a Jira group, and split by day, week or month. Totals on both axes.
What was actually done
The Worklogs view turns the grid into worklogs as rows: date, author, issue, hours and the comment, sortable and filterable. Export the grid or the list to CSV: the list exactly as it is on screen.
Where time is missing or overspent
Switch on Gaps to mark working days on which someone logged no time, and Overspend to flag issues over their original estimate. Each mark says what it means on hover, and a legend explains it.
How it counts
A worklog counts on the day it started
In the viewer’s time zone, or in each author’s. The rule is printed under every report: “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 an issue 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.
Rows, columns and periods
Up to two levels of rows, a split across the columns, and a total on every row and column, plus a grand total.
Rows
- Issue
- Person
- Space
- Epic
- Issue type
- Status
- Priority
- Component
- Label
- Select or radio field
- Jira group
Up to two levels, such as person then issue, or epic then person.
Columns
- Total only
- Day
- Week
- Month
A day split needs a period of 62 days or less. Weeks start on Monday unless the site or the report says otherwise.
Periods
- Today
- Yesterday
- This week
- Last week
- This month
- Last month
- Last 7 days
- Last 30 days
- Last 90 days
- This quarter
Five are chips; the rest are under More periods, with a Custom range of up to 400 days. Rolling periods move with the calendar.
Hours
- 7.5h
- 7h 30m
- 1d 2h
A day is the site’s working-day length: 8 hours unless an admin changes it.
What’s included
Reports
- Report page
- Apps › Logline opens on install with the last 30 days, every space you can see, by person then issue, split by week.
- Space reports
- The same report, limited to one space, in every space’s sidebar.
- Issue panel
- Time on an issue and its children, by person and by week, against the estimate.
- Worklogs view
- Every worklog as a row, newest first: date, author, issue, hours and comment. Sort it, and filter by comment, issue or author.
- Saved reports
- Mine, Shared with me and All. Share a report with chosen people, Jira groups or everyone on this site.
- Gaps and overspend
- An amber 0h on an empty working day, a red percentage on an issue over its estimate, each with a legend. Off by default.
Also
- CSV export
- Download CSV or Copy, built in your browser: the worklog list exactly as shown, the timesheet as a flat list a spreadsheet can add up.
- Extra columns
- Original estimate, Remaining, Time spent (all time) and Work ratio on issue rows.
- Show worklogs
- On any bottom-level row, lists its worklogs under it: date, author, hours and the comment.
- Stated limits
- Up to 10,000 issues and 50,000 worklogs per report, read in steps with a progress bar. Never a partial total.
- Admin settings
- Time zone rule, week start, working-day length and days, hours format, and who may share reports.
- Your data stays put
- Built on Forge with no data egress. Everything it stores stays in Forge storage, hosted by Atlassian.
Coming from a Connect worklog app?
If your current worklog report is a Connect app, Atlassian is showing a “might stop working” notice for it. Logline is built on Forge and mirrors the views such a report offers.
| What you used | In Logline |
|---|---|
| Timesheet grouped by a field | Rows: up to two levels, from person, issue, epic, space, type, status, priority, component, label, a select field or a Jira group |
| Daily, weekly or monthly split | Columns: day, week or month, with totals |
| Fixed and rolling date ranges | Period: the chips, More periods, or a custom range |
| Worklogs as rows, with comments | View: Worklogs |
| Work ratio column | Extra columns, and Overspend |
| Grouping by Jira group | People: Jira groups, then Rows: Jira group |
| Saved reports, public or restricted | Save, then Share |
| Excel export | Download CSV |
| Service management spaces | Every space you can see, service spaces included |
Both apps can run side by side while you compare totals. How to switch
Pricing
Free up to 10 users
From $0.90 per user a month above that
- Billed by Atlassian
- Every feature on the free tier
- 30-day free trial
Questions
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.
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 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.
Does it work in team-managed and company-managed spaces (projects)?
Yes, both, and in service management spaces too. A report covers every space you can see, and the same report sits in every space’s sidebar, limited to that space.
Which day does a worklog count on?
The day it started, in the report’s time zone. By default that is the time zone of the person viewing, from their Jira profile; a report or the site settings can use each author’s own time zone instead. The rule in force is printed under every report.
Why can two people see different totals for the same report?
A shared report always runs as the person viewing it. Jira’s permissions decide which worklogs each viewer sees, including worklogs restricted to a group or role, so nobody sees a worklog, an issue or a comment they could not see in Jira. Two people can therefore see different totals for the same report, and the report says so.
Does it change my worklogs or issues?
No. Logline only reads. It has no write permission, so it cannot create, change or delete a worklog, an issue or a setting in Jira.
Can I export a report?
Yes, to CSV. Download CSV and Copy take what is on screen. The Worklogs view goes out exactly as shown, after the filter and the sort; the Timesheet goes out as a flat list a spreadsheet can add up and pivot, one line per row with the row above it named beside it, then the totals line. Hours are numbers in decimal hours, so a spreadsheet can add them up, and dates are YYYY-MM-DD. The files are built in your browser; nothing is sent anywhere.
Is there a size limit?
Yes. A report reads at most 10,000 issues and 50,000 worklogs. Over that, Logline says so and asks for a shorter period or a smaller scope; it never shows a partial total. A big report is read in steps, with a progress bar, each step well inside Forge’s time limit for one call.
Where is my data stored?
In Forge storage hosted by Atlassian: the site’s settings, saved reports, when each person last opened each report, and report snapshots, kept per person, served for at most 10 minutes and deleted by Forge storage a minute after that. Saved reports and settings stay until deleted or the app is uninstalled. No data leaves Atlassian.
What can a Jira admin change?
Under Jira settings › Apps › Logline settings, for the whole site: the time zone a worklog’s day is counted in, the first day of the week, the working-day length and the working days, the hours format, and who may share reports. Reports use the new settings the next time they are opened.
What does it cost? Is there a free trial?
Logline is free for sites with up to 10 Jira users, with every feature. Above that it is $0.90 per user a month for users 11 to 100, $0.45 for users 101 to 250 and $0.18 for each user above 250, billed by Atlassian, after a 30-day free trial.
Is there a discount for large sites?
Yes. Above 100 users the per-user rate steps down: $0.45 for users 101 to 250, $0.18 for each user above 250.