Skip to content
Menu
HelpGaps and overspend

Gaps and overspend

Gaps is a toggle above the timesheet, filled while on (with Expected, in Rows and columns). It is off by default and one click on, and it is written out as text, not only colour: each mark says what it is when you point at it, and so does the toggle. Over the estimate is the Columns chip’s: Original estimate, Logged (all time) and Remaining, all three picked for a new report.

A toggle shows only while the rows and columns fit it: Gaps once people are rows and the columns are days, Expected once people are rows. Until then it is not there. Pressing one never changes the rows or the columns: choose people as rows, and Day under Per, and the toggle appears (Show report is the one exception, below). A change that leaves a toggle unable to show turns it off, and a link or saved report that carries one it cannot show opens without it.

Gaps

Gaps need days as columns and people as rows, and days need a period of 62 days or less. A working day (Monday to Friday unless an admin changes it) before today on which a person logged nothing is marked with a yellow 0m; today is not marked until it is over, so nobody shows a gap at nine in the morning; pointing at it says “No time logged”. Pointing at the Gaps toggle says what it marks.

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 team’s week with Gaps, Expected and Short days on: the gaps and short days in yellow

With Gaps on, Short days, offered only then, also marks a working day on which a person logged less than a working day (the working-day length in Logline settings), in the same yellow with the hours logged; pointing at it says how short it is.

With Gaps on, a day on which a person logged more than 24 hours is marked in red with its hours; pointing at it says “more than a day holds. Check for duplicate worklogs”.

To see people who logged nothing at all in the period, limit the report to people or groups: then everyone in them gets a row. With Everyone, the report says who is missing, with Choose people. Limiting a report to chosen people or a Jira group with Show report, people as rows, switches Expected on, and Gaps with the columns on days where the period has 62 days or fewer: that is a team’s timesheet, and the one time Logline changes the columns for Gaps. Gaps off puts the columns back.

Over the estimate

The Columns chip adds, on work item rows, Original estimate, Logged (all time) and Remaining, in that order, as the work item panel’s table has them. Logged (all time) has a lozenge after its hours that marks every work item’s time spent as a share of its original estimate (the work ratio): green up to the estimate, yellow up to 120% of it, such as 117%, and red past that; pointing at it says “117% of estimate”. A work item with time logged and no original estimate says No estimate in that cell, in grey, once any work item in the report has an estimate; pointing at it says “Time logged with no original estimate”. The downloads keep the cell empty.

Remaining has a lozenge after its hours, where the work ends: the time logged plus the remaining estimate as a share of the original estimate, in the same colours. A row that holds work items, such as an epic, a space or a person, says how many of them are over, such as 2 over, in the colour of the one furthest over; pointing at it names them, and they show while Remaining is picked. Sort › Remaining % puts the rows with the work furthest over first, at every level, while Remaining is picked; the order is saved with the report.