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 issue has its worklogs. The Work log tab in an issue’s activity lists every worklog on it, with its author, date, time and comment. One issue 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 issues 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 issues. The trouble is the hours beside them: the Time Spent column
is each issue’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 issue, with the same all-time Time Spent; the all-fields export adds each issue’s worklogs as Log Work columns, one cell per worklog with its comment, date, author and seconds, every worklog the issue 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 issue’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 issue:
- Open Apps › Logline. The last 30 days are already there, every space you can see, by person then issue, split by week.
- Pick Last month (or More periods, or a custom range of up to 400 days).
- Rows is Person, Then by Issue or Epic. Columns on Auto gives a column per week for a month and per month for a quarter; Total only gives one figure a person.
- Each person’s row shows their Total first, then the period’s columns. The arrow on a row opens their issues, and on an issue its worklogs, with each comment.
- For your own hours only: Edit report › People › Only me. For a team: Jira groups or Chosen people.
- Save it, then open it from Saved reports next month: Last month moves with the calendar. Download 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 the rule is printed under every report (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 issues 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.
