Skip to content
Menu
HelpJira worklog report by user and month

Jira worklog report by user and month

Checked against Atlassian’s documentation on 7 October 2026.

Someone needs last month’s hours per person: for payroll, a contractor’s invoice, or a manager’s review. On Atlassian Community it reads “our bookkeeper does NOT want to add up hundreds of logs by hand” (Community, June 2025), or “logged 4 hours … in December and then 7 more hours in January. I want to … see the 7 hours” (Community, January 2026). This page says what Jira gives you by itself, how far a search and an export go, then what Logline does.

What Jira does by itself

  • Each work item has its worklogs. The Work log tab in a work item’s activity lists every worklog on it, with its author, date, time and comment. One work item at a time.
  • The Time tracking report is per version, and only in company-managed spaces (Atlassian); the request for team-managed spaces, JSWCLOUD-18009, has been open since 2019. It compares estimates with time spent; it does not split hours by person or by month.
  • There is no report of hours per person per period. The request, JRACLOUD-97253, is gathering interest, and says teams “export data to CSV and manually process it”.
  • Atlassian Analytics can query worklogs, on Jira Enterprise.

A search and an export

JQL finds the work items someone logged time on in a month:

worklogAuthor = currentUser() AND worklogDate >= 2026-09-01 AND worklogDate <= 2026-09-30

For a team, worklogAuthor in membersOf("web-team"). That gives the right work items, give or take two catches that Jira worklogs in a date range explains. The trouble is the hours beside them: the Time Spent column is each work item’s all-time total, from every author. The 7 hours in January above show as 11.

The export does not fix that. Its CSV has one row per work item, with the same all-time Time Spent; the all-fields export adds each work item’s worklogs as Log Work columns, one cell per worklog with its comment, date, author and seconds, every worklog the work item ever had. Splitting those cells into rows and keeping one person’s month is spreadsheet work, every month; Export Jira worklogs to Excel walks through it.

Someone technical can read each work item’s worklogs through the REST API, GET /rest/api/3/issue/{issueIdOrKey}/worklog with startedAfter and startedBefore (Atlassian), and add them up in a script. Two things to settle first: which time zone decides the day a worklog counts on (an evening worklog in New York is the next morning in UTC), and the worklogs restricted to a group or role, which only some people can read.

With Logline

Logline is our app. It turns the worklogs your teams already log into a report by person, period and work item:

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. The last 30 days are already there, every space you can see, by space then work item, in one Total column.
  2. Pick Last month under Period (or another period, or a custom range of up to 400 days).
  3. Set Rows to Person, Then by to Work item or Epic, and Per to Auto: a column per week for a month and per month for a quarter; Total only gives one figure a person.
  4. Each person’s row shows their Total first, then the period’s columns. The arrow on a row opens their work items, and on a work item its worklogs, with each comment.
  5. For your own hours only: on the scope row, Whose time › Only me. For a team: Jira groups or Chosen people.
  6. Save it, then open it from Saved reports next month: Last month moves with the calendar. Download, then Excel, takes it to a spreadsheet.

How it counts, so the figure stands up when someone checks it:

  • A worklog counts on the day it started, in the viewer’s time zone or in each author’s, and every report names the time zone it counts in (Periods, days and time zones).
  • Hours are added up in seconds and rounded once, so a total matches Jira’s worklogs to the minute.
  • Every read is made as the person viewing, so a worklog Jira hides from them is not counted, and a shared report says when that can differ between viewers.
  • A report reads up to 10,000 work items and 50,000 worklogs; above that it says so and asks for a shorter period, rather than showing a partial total.

The other row groupings and the extra columns are in Rows and columns. More on the Logline home page.

A Logline report on 1 to 30 September, from its scope row down: Scope set to Spaces with ACME, INT and NWND chosen, Whose time Everyone, Period 1 Sep – 30 Sep with its arrows, Show report, then Save, Reports, Copy link and Download on the same line; under it one grey line, “1 Sep – 30 Sep · 447 worklogs · Counted in America/New_York”, with How this is counted and Recalculate. Then the Timesheet tab and its chips: Rows Epic, Then by Work item, Per Total only, Billable only, Sort Remaining %, Descending and Columns. Rows are epics, then work items, with Total, Billable, Amount and the estimate columns, the Total row first: 652h 45m, 404h 30m of it billable at 62%, USD 56,655. ACME-1 Q4 storefront, “2 over”, has 223h 45m, 195h of it billable, its work items furthest over first: ACME-2 Checkout redesign, 14h logged against 12h estimated, a yellow 117%, and a red 133% where it ends. ACME-7 Order history page, 19h, is opened to its nine worklogs, each with its date, Mitch Davis or Alana Grant, the hours and the comment, such as “Tue 1 Sep 14:00 · Mitch Davis · 2h · Order list layout”. NWND-1 Mobile app v2 has 162h 30m, 134h of it billable.
September in Logline by epic, then work item; Rows › Person gives the same month by user.

Try it on your own worklogs

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