Skip to content
Menu
HelpExport Jira worklogs to Excel, one row per worklog

Export Jira worklogs to Excel, one row per worklog

Checked against Atlassian’s documentation on 7 October 2026.

For an invoice, a payroll run or an audit you need the worklogs themselves in a spreadsheet: one row each, with its date, author, work item, hours and comment, for one period. Jira’s export is built around work items, not worklogs. This page shows how to get from one to the other with Jira’s own tools, where it gets slow, then what Logline does.

What Jira’s export gives you

Search for the work items first. JQL finds every work item with time logged in a period, by anyone or by a team:

worklogDate >= 2026-09-01 AND worklogDate <= 2026-09-30 AND worklogAuthor in membersOf("web-team")

Then Export from the search results:

  • The current fields export gives one row per work item. Its Time Spent is the work item’s all-time total from every author, not the time logged in your period (Community, January 2026).
  • The all-fields export adds the work item’s worklogs as Log Work columns: one cell per worklog, holding its comment, date, author and time in seconds, separated by semicolons (look at one cell before you split them). Every worklog the work item ever had is there, from every author and every month.

From work item rows to worklog rows

To turn the all-fields export into one row per worklog:

  1. Open the file in Excel and keep the key, the summary and the Log Work columns.
  2. Unpivot the Log Work columns into rows (Power Query’s Unpivot Columns does it), so each worklog is a row beside its work item.
  3. Split each cell on the semicolon into comment, date, author and seconds.
  4. Turn the seconds into hours (divide by 3600) and the date text into a date.
  5. Filter to your period and your people. Keep the filter and the steps: next month starts again from step 1.

Three things to check before you trust the result. A comment with a semicolon in it splits into too many columns. The day a worklog counts on depends on a time zone: an evening worklog in New York is the next day in UTC, so a month’s edges can move. And the date in the file can be the day a worklog was entered, not the day it was logged for (JRACLOUD-77926, open): time logged on Monday for last Friday lands on Monday, so a timesheet built from the file puts it on the wrong day.

Someone technical can skip the spreadsheet steps with the REST API: the work item search for the keys, then each work item’s worklogs from GET /rest/api/3/issue/{issueIdOrKey}/worklog with startedAfter and startedBefore (Atlassian).

With Logline

Logline is our app. Its Worklogs view is the export above, already made, for any period and scope:

Jira with its left sidebar open on Apps, Logline picked under Your apps. Beside it, the Logline page: its scope, the spaces ACME, INT and NWND, Whose time, the period 1 Sep to 30 Sep, Show report, the Save, Reports, Copy link and Download buttons, 447 worklogs, the Timesheet tab with Rows Space then Work item, and the first rows of the grid: the Total row, then Acme Website and its work items.
Apps › Logline: Jira’s sidebar open on Apps with Logline picked, and the report beside it
  1. Open Apps › Logline, or the Logline tab in a space, and pick the period: Last month, another in the Period list, or a custom range.
  2. Open the Worklogs tab. Every worklog in the report is a row: Date, Author, Work item, Hours and Comment, newest first.
  3. Sort it, or filter by a word in the comment, a work item or an author. The count line adds up what is shown, such as “10 of 116 worklogs · 10h”. With a billable rule, Billable only keeps the billable worklogs, and each row has its rate and amount.
  4. Download, then Excel, takes the list exactly as shown, after the filter and the sort. CSV does the same as a CSV file.

What is in the file:

  • Hours are numbers in decimal hours, so the spreadsheet can add them up.
  • In the Excel file the dates are real dates, so a pivot by month needs no conversion, and Started is the date and time each worklog started. Each work item key links to the work item. The sheet has a bold header row that stays in view.
  • The Timesheet tab exports too: one line per row with the row above it named beside it, then the totals line, ready for a pivot. Its Excel file has a second sheet, Worklogs, with every worklog in the report.
  • The files are built in your browser; nothing is sent anywhere.

A report reads up to 50,000 worklogs; above that Logline says so and asks for a shorter period or a smaller scope. Each column is described in Exporting to Excel, CSV and PDF, and the Worklogs view in The Worklogs view. For hours per person rather than worklog by worklog, see Jira worklog report by user and month. More on the Logline home page.

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.
A space’s Logline tab: September’s total with Save, Reports, Copy link and Download, then a work item opened to its worklogs.

Try it on your own worklogs

Free for up to 10 users, then billed per user by Atlassian.