A weekly Jira timesheet for your team

Every Monday a team lead wants the same table: last week, one row per person, a column per day, the total, and who is short. 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 issues. Last week’s issues 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 issues, not hours per person, and each issue’s Time Spent is its all-time total from every author.
A dashboard shows the filter, through Jira’s Filter results gadget: the same issue list, on the page the team already opens.
Who logged nothing is not something a search can find: a person with no worklogs matches no issue, so they are simply absent. Someone has to compare the list with the team by hand.

From there, the usual route is the export and a spreadsheet: one row per issue, 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:

Open Apps › Logline and pick Last week. Columns on Auto gives one column per day, Monday to Sunday (or from the week start your site sets).
Edit report › People › Jira groups, pick the team’s group, then Show report. Picking people switches Gaps and Expected on by themselves.
Rows is Person; Then by Issue if you want each person’s issues under them. The arrow on a row opens it.
Save it as the team’s week and Share it with the group.

What each person’s row shows:

Total first, then Expected: the working days so far in the period times the working-day length in Logline settings (8 hours unless an admin changes it).
Against expected, in words: “40h under” in a yellow lozenge for someone short, the hours over as text for someone over.
Gaps: a yellow 0h on a working day, up to 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.
Overspend, if you switch it on: an issue over its original estimate shows its work ratio in red, such as 117%.

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 People 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 Excel if it goes into payroll: after the names come Total, Expected and Logged − expected, then the days.

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 under Edit report:

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.