I previously had JQL that could be used to get all of the work log entries from a Jira ticket but I no longer have that query. Can someone share with me the syntax to get work log entries in detail that can be exported for analysis?
Hi @Kim Clark
JQL can't return the work log entries themselves, only the work items that have them. So the trick is to find the work items with the worklog fields, then export.
For example: worklogDate >= "2026-10-01" AND worklogAuthor = currentUser() (or just key = ABC-123 for one ticket). Field details: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/
Then use Export > Export CSV - all fields. Each entry lands in its own "Log Work" column as comment;date;author;seconds.
One catch: that date is when the entry was created, not the date the work was logged for (JRACLOUD-77926: https://jira.atlassian.com/browse/JRACLOUD-77926). If you need the real "started" date, the Get issue worklogs REST endpoint returns it: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-worklogs/
Hi @Kim Clark,
To add to Thanasis's answer, if your goal is to export individual worklog entries for detailed analysis, I would recommend using the Jira REST API rather than relying on JQL and CSV exports.
For a specific issue, you can retrieve its worklogs using:
GET /rest/api/3/issue/ABC-123/worklog
The response includes useful details such as the worklog author, time spent, started date, description, and worklog ID.
For multiple issues, you can first use JQL to identify the relevant issues, then retrieve their worklogs through the API and export the results to CSV or Excel.
One important advantage is that you can analyze individual worklog entries rather than aggregated time-tracking values.
Also, keep in mind that worklogDate in JQL refers to the date the work was logged for, while the API provides separate started and created timestamps.
Hope this helps! Regards, Gor
Hi Kim, one more route if you want the entries themselves and would rather not script the REST call Gor described.
The catch Thanasis mentioned is the one that usually skews this kind of analysis: the date in the CSV "Log Work" column is when the entry was created, not the day the work was logged for. The worklog API returns the real "started" date, so whatever you use, make sure it reads from there.
Disclosure: I'm the developer of ArtUp Reports, an export app on the Atlassian Marketplace. Its built-in Excel layout "Work logs" writes one row per work log entry with the work item key, summary, author, started date, hours and comment, for any JQL you give it, for example worklogDate >= "2026-10-01". It reads every entry of each work item through the worklog API, not only the ones returned with the search. One thing to keep in mind: the JQL selects work items, so a work item with a single entry in October brings all its entries. Filter the Started column in Excel to keep just your period.
worklogDate >= "2026-10-01"
Drafted with an AI assistant and reviewed by me.
@Kim Clark
I’d add a note on the “for analysis” part, because that’s where the CSV route usually takes the most time. Each entry lands in one text cell (comment;date;author;seconds). Before you can total anything, you have to split those cells, turn seconds into hours and build the pivot yourself.
Better Excel Exporter has a built-in “Worklog Report” option in its export menu. You run it on the same JQL from the accepted answer, and you get a finished report instead of a raw file:
I think the template is the part that saves the most time over the months. You can copy and change it once, for example, to group by epic or component, and every later export comes out in that layout. If this turns into a monthly report, the free Better Excel Automation can email the .xlsx on a schedule.
The docs cover the template setup. I’m one of the people building this at Midori, so feel free to drop me a line at levente.szabo@midori-global.com if you want help shaping the report around your analysis.
It looks like you're new here. Sign in or register to get started.
