Skip to content
Menu

Hours logged in a Jira space per month

Checked against Atlassian’s documentation on 12 October 2026.

A space is often a client, a product or a cost centre, and someone needs its hours month by month. On Atlassian Community it reads “a ticket … that started in January but the work continues over the course of several months, how do I see the hours the team has done?” (Community, April 2026). This page says what Jira gives you for a space, how far a search goes, then what Logline does.

What Jira does by itself

  • No hours per space per month. A space’s reports include the Time tracking report, which works per version and compares estimates with time spent (Jira’s Time tracking report has the details). Jira has no report of hours per period; the request, JRACLOUD-97253, is gathering interest.
  • A search finds the month’s issues. project = ACME AND worklogDate >= startOfMonth(-1) AND worklogDate < startOfMonth() lists the issues in the space with time logged last month. Save it and it moves with the calendar.
  • The hours beside them are all-time. The ticket that started in January shows every hour since January, on screen and in the export, so adding up the Time spent column counts earlier months again.

The month’s hours come from the worklogs: each issue’s from GET /rest/api/3/issue/{issueIdOrKey}/worklog with startedAfter and startedBefore (Atlassian), added up in a script or a spreadsheet, once for each month. Jira worklogs in a date range says what else to watch for in that search.

With Logline

Logline is our app. There are two ways in:

  • In the space: open its Logline tab. It is the same report, limited to that space, opening on the last 30 days. Pick This year or Last quarter under More periods, and Columns on Auto gives a column per month.
  • Every space at once: open Apps › Logline, set Rows to Space, Then by to Epic or Person, and pick the period. Columns › Month splits any period by month, and a custom range reaches back up to 400 days.

Each space’s row is the time logged in the period on its issues, and every month’s column only the time logged in that month. The arrow on a row opens what is under it, down to each worklog and its comment.

A few things to know:

  • An issue moved to another space counts under the space it is in now, in every period, including the months before the move.
  • With a billable rule and hourly rates set, each space’s row also shows its billable hours and their amount; see Billable hours in Jira.
  • A report saved on a space’s tab is listed in that space’s own Saved reports.

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

The same month by space, then epic, with a total row: Acme Website 270.5h, all billable, USD 40,575.00; Internal 108.75h, none billable; Northwind App 197h, 134h billable, USD 16,080.00; in all 576.25h, 404.5h billable, USD 56,655.00, with a column per week.
Rows by space, then by epic, split by week, with billable hours and amounts.

Logline is not on the Marketplace yet. Get one email the day it’s live.