Skip to content
Menu
HelpA weekly Jira timesheet for your team

A weekly Jira timesheet for your team

Checked against Atlassian’s documentation on 7 October 2026.

New to logging time in Jira? Start with Log time on a work item.

Every Monday a team lead wants the same table: last week, one row per person, a column per day, the total, and the days still empty. Jira keeps every worklog that goes into it, but has no timesheet view. This page says how close Jira’s own tools get, where they stop, then what Logline does.

What Jira does by itself

  • No timesheet. Jira Cloud has no view of hours per person per day. The request for a report of time per person per period, JRACLOUD-97253, is gathering interest.

  • A filter finds the work items. Last week’s work items with time from the team:

    worklogAuthor in membersOf("web-team") AND worklogDate >= startOfWeek(-1) AND worklogDate < startOfWeek()

    Save it and it moves with the calendar. But it lists work items, not hours per person, and each work item’s Time Spent is its all-time total from every author.

  • A dashboard shows the filter, through Jira’s Filter results gadget: the same work item list, on the page the team already opens. Hours logged per person on a Jira dashboard covers the other gadgets.

  • Who logged nothing is not something a search can find: a person with no worklogs matches no work item, so they are simply absent. Someone has to compare the list with the team by hand; Who hasn’t logged time in Jira this week has Atlassian’s reminder workaround.

From there, the usual route is the export and a spreadsheet: one row per work item, the worklogs split out of their cells, a pivot by person and day, redone every week. Export Jira worklogs to Excel shows that route, and Jira worklog report by user and month the REST API one.

With Logline

Logline is our app. The weekly timesheet is a report you build once and open in two clicks every Monday after that:

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 and pick Last week, then set Per to Auto for one column per day, Monday to Sunday (or from the week start your site sets).
  2. On the scope row, Whose time › Jira groups, pick the team’s group, then Show report. Picking people switches Gaps and Expected on by themselves.
  3. Rows is Person; Then by Work item if you want each person’s work items under them. The arrow on a row opens it.
  4. Save it as the team’s week and Share it with the group.
Logline over Harbor Labs for Monday 28 September to Friday 2 October, Whose time Everyone, Rows Person, Then by Work item, Per Day, sorted by Total, most first: the Total row, 147h 30m, then Kevin Campbell open, 41h, 29h of it billable at 71%, with his nine work items and the hours each took on each day, such as HLAB-8 Push notifications, 9h. HLAB-11 Team meetings is opened to its five worklogs, 15m of “Stand-up and planning” each morning from Monday to Friday, each under its day. Then Mitch Davis, 40h, Alana Grant, 34h 30m, and Cassi Owens, 32h, closed on their day totals.
A working week by person, then work item, a column per day: Kevin Campbell open, Team meetings opened to a worklog a day

What each person’s row shows:

  • Total first, then Expected: the working days before today in the period times the working-day length in Logline settings (8 hours unless an admin changes it), plus what the person has logged today, up to a full day. A day that is not over counts neither against anyone nor for them.
  • Against expected, in words: “40h under” in a yellow lozenge for someone short, the hours over as text for someone over.
  • Gaps: a yellow 0m on a working day, before today, on which someone logged nothing. Switch on Short days too and a working day with less than a full day logged is marked in yellow with its hours.
  • Columns, picked for a new report: each work item shows its work ratio, green within its original estimate, yellow up to 120%, such as 117%, and red past that.

Two things it does not know: holidays and leave. Logline reads worklogs and nothing else, so a person on holiday shows as under; the Expected switch says so on hover.

Why the group matters: with Whose time on Everyone, the report is built from who logged time, so the person who logged nothing is the one who is missing. Logline says so above the table, with a Choose people button.

Every Monday

  • Open Saved reports and the team’s week: Last week has moved on by itself.
  • Or put it on a dashboard with the Logline gadget: the report’s total and its biggest rows, as each person viewing sees them, with Expected and Against expected on person rows when the report was saved with them, and Open in Logline for the whole grid.
  • Download, then Excel, if it goes into payroll: after the names come Total (h), Expected (h) and Against expected (h), then the days, each with “(h)” too; the totals line adds up Expected and Against expected.

The settings behind the week

A Jira admin sets these once for the site, in Logline settings, and a report can override some of them on its scope row or in How this is counted:

  • the day the week starts, and which days are working days;
  • the working-day length that Expected multiplies;
  • whether a worklog’s day is counted in the viewer’s time zone or in each author’s, which matters for a team across time zones: an evening worklog in New York is the next morning in Riga.

Everyone sees only the worklogs Jira lets them see, so a shared report’s totals can differ between viewers, and the report says so. The marks are explained in Gaps and overspend, sharing and the gadget in Saved and shared reports. More on the Logline home page.

A timesheet of one working week with Rows set to Person and Gaps, Expected and Short days switched on: the Total row first, 147h 30m, then a row per person, with Total, Expected, Against expected and a column per day from Monday 28 September to Friday 2 October. Alana Grant 34h 30m, 5h 30m under; Cassi Owens 32h, 8h under; Kevin Campbell 41h, 1h over; Mitch Davis 40h, exactly as expected; each against 40h. Cassi’s Wednesday shows a yellow 0m, and Alana’s 6h Tuesday and 4h 30m Friday are yellow too.
A working week for four people, a day per column: each person’s total against 40h expected, a yellow 0m on a day one of them logged nothing, and the short days in yellow too.

Try it on your own worklogs

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