Skip to content
Menu

Who hasn’t logged time in Jira this week

Checked against Atlassian’s documentation on 12 October 2026.

Before payroll or an invoice goes out, a team lead needs the names of the people who have not logged their week. Jira keeps every worklog that was logged; it has no list of the people who logged nothing. This page shows Atlassian’s own workaround, where it stops, then what Logline does.

Why a search cannot find them

JQL returns issues. A search such as worklogAuthor in membersOf("web-team") AND worklogDate >= startOfWeek() lists the issues the team logged time on this week, and a person with no worklogs this week matches no issue, so they are absent from the result. Finding them means comparing the result with the team, by hand.

Atlassian’s workaround: a reminder by Automation

Atlassian’s knowledge base sends a weekly reminder to log work with two searches and a scheduled rule:

  1. A saved filter, filterA, finds the issues with work logged this week: project = "Project A" AND worklogDate >= startOfWeek().
  2. A second search finds the issues updated this week that are not in it: project = "Project A" AND updated >= startOfWeek() AND filter != filterA.
  3. An Automation rule runs every Friday at 17:30, runs the second search and emails each issue’s assignee.

The article says it finds such issues “in a limited capacity”. In practice:

  • It reminds the assignee of an issue that changed, which is a guess at who worked on it. Someone whose issues did not change, or who worked on an issue assigned to someone else, gets no reminder.
  • It says nothing about hours: someone who logged 2 hours of a 40-hour week is not on the list.
  • It cannot tell a missing timesheet from a day off.

The reminder can still be useful on its own. For a list of who is short and by how much, the hours have to be added up per person, which is the weekly timesheet route.

With Logline

Logline is our app. A report limited to the team gives every member a row, including the ones who logged nothing:

  1. Open Apps › Logline and pick This week or Last week.
  2. Edit report › People › Jira groups, pick the team’s group, then Show report. Picking people switches Gaps and Expected on.
  3. With Rows on Person, each working day before today on which someone logged nothing shows a yellow 0h, and Against expected says how far short each person is, such as “40h under” in a yellow lozenge.
  4. Switch on Short days to mark, in the same yellow with its hours, a working day with less than a full working day logged.
  5. Save it and Share it with the group, or put it on a dashboard with the Logline gadget: a report saved with Expected and people as rows shows each person’s Expected and how far under or over it they are.

Today is not marked until it is over, so nobody shows a gap at nine in the morning. Holidays and leave are not known to Logline: a person on holiday shows as under, and the Expected switch says so on hover.

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 Choose people.

The marks are described in Gaps and overspend. More on the Logline home page.

A Last week timesheet with Rows set to Person and Gaps, Expected and Short days switched on: a row per person and a total row, with Total, Expected, Against expected and a column per day from Monday 28 September to Sunday 4 October. Alana Grant 34.5h, 5.5h under; Cassi Owens 32h, 8h under; Kevin Campbell 41h, 1h over; Mitch Davis 40h, exactly as expected; each against 40h; 147.5h in all. Cassi’s Wednesday shows a yellow 0h, and Alana’s 6h Tuesday and 4.5h Friday are yellow too.
Last week for four chosen people, a day per column: a yellow 0h on a day nobody logged, and each person’s total against 40h expected.

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