Export Jira worklogs to Excel, one row per worklog

For an invoice, a payroll run or an audit you need the worklogs themselves in a spreadsheet: one row each, with its date, author, issue, hours and comment, for one period. Jira’s export is built around issues, 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 issues first. JQL finds every issue 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 issue. Its Time Spent is the issue’s all-time total from every author, not the time logged in your period (Community, January 2026).
• The all-fields export adds the issue’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 issue ever had is there, from every author and every month.

From issue 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 issue.
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.

Two things to check before you trust the result. A comment with a semicolon in it splits into too many columns. And 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.

Someone technical can skip the spreadsheet steps with the REST API: the issue search for the keys, then each issue’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:

1. Open Apps › Logline, or the Logline tab in a space, and pick the period: Last month, More periods, or a custom range.
2. Open the Worklogs tab. Every worklog in the report is a row: Date, Author, Issue, Hours and Comment, newest first.
3. Sort it, or filter by a word in the comment, an issue 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 Excel takes the list exactly as shown, after the filter and the sort. Download CSV does the same as a CSV file, and Copy puts it on the clipboard so it pastes into a spreadsheet one value per cell.

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. The file has one sheet, named Logline, with 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.
• 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 and CSV, 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.