Rows and columns
A report is a grid: the rows say what the hours are grouped by, the columns how they are split over the period. Change either on the line above the timesheet: Rows, Then by and Per. They change at once, without reading Jira again, except the first time a report is grouped by a field it has not read yet (below).
Rows
Person, work item, space, epic, parent, work type, status, priority, resolution, component, label, fix version, sprint, assignee, reporter, creator, Jira group, Team (Jira’s Team field, each team by its name), Organization (Jira Service Management’s Organizations field, each organization by its name; a request with two counts under each), a choice field (a select list, radio buttons, checkboxes or a labels field, single or multiple) or a single user picker. Rows and Then by list the common rows first (Space, Epic, Work item, Person, Team, Organization and Sprint where the site has them; Space only where the worklogs come from more than one space, so not on a space’s own tab), then More for the rest of Jira’s own, with a search box to find one by name. Custom fields are under Fields only once a Jira admin picks them under Fields in Rows in Logline settings, the Client field of the budgets included (a report already grouped by a field keeps it listed). Only fields with a few values to count under are offered: a text field would give a row per thing written, so it is a column in the Worklogs view instead, never a row. Up to two levels (Rows, then Then by), such as space then epic, person then work item, or epic then person. Then by offers only what splits the row: under a work item, only who logged its time (Person, or a Jira group), since its space, epic or status is one value; under a parent, everything but Epic, which its children share. A new report opens by space, then work item; on a space’s tab, which is one space, by epic, then work item. A saved report, and a link, keep their own rows. The arrow at the start of a row folds its children away and back. A space row’s name, after a folder, opens Logline’s tab in that space on the same report.
Jira group needs the report limited to Jira groups: pick them under Whose time on the scope row first. Until then it is not in either list. A link or saved report grouped by Jira group without them opens without that level.
A parent row shows its parent as Jira shows a work item, with its type icon, key and summary; an assignee, reporter or creator row shows the person. Work items without one are together under “No parent”, “Unassigned”, “Unresolved”, “No sprint”, “No team” and so on, always last. Sprint is offered on sites with Jira Software.
Parent, resolution, fix version, sprint, assignee, reporter, creator, Team, Organization, choice fields and user pickers are read from Jira only when a report uses them, so the first time you choose one the report reads its worklogs again, with a progress bar; switching back and forth after that reads nothing more.

A worklog under two or more rows (two labels, two fix versions, two sprints, a person in two groups) counts in each of those rows, but once in every total. The report says so when it happens.
Per
Per picks the period’s columns. Auto follows the period: by day for Today, Yesterday, a week or the last 7 days; by week for a month, the last 30 or the last 90 days; by month for a quarter or a year; a custom range by its length (up to 7 days by day, up to 92 by week, longer by month), except that three or more whole calendar months, such as a quarter, are by month. The Per chip says what Auto gives, such as “Auto (Day)”. Or choose Total only, or a split by Day (listed only for a period of 62 days or less), Week or Month; a saved report keeps the split it was saved with. A new report opens on Total only. Day columns name the month on the first day and on each 1st: “Mon 28 Sep”, “Tue 29”, … “Thu 1 Oct”.
Total comes right after the row’s name, so it is in view however many days the period has; then the period’s columns. The totals row comes first, shaded, with a total for every column and a grand total. A row that adds up the rows under it is shaded the same. Figures are set to the right of their column, so they line up.
Columns and Sort
Columns, at the end of the line above the timesheet, picks the estimate columns work item rows show: Original estimate, Logged (all time) and Remaining, as Jira shows them, beside the period’s hours. All three are picked for a new report. A lozenge follows the hours of two of them: after Logged (all time) the work ratio, Jira’s time spent over the original estimate from every date, and after Remaining where the work ends, the time logged plus the remaining estimate over the original estimate; pointing at either header says so, and the lozenges are green up to the estimate, yellow up to 120% of it and red past that. The downloads keep the work ratio as a column of its own. The columns go on work item rows: pick one while no level is a work item and Then by becomes Work item. With Remaining picked, a row that holds work items says how many of them are over their estimate, such as 2 over (Gaps and overspend).
When the first rows are spaces, epics or the client field and some of them have a budget, five more columns follow Amount: Budget, Spent, Left, % used and At completion (Set a budget). The members of one chosen group also see Cost and Margin there (See cost and margin).
Sort, with its direction beside it, orders the rows at every level, one choice per column: Name (a work item by its summary), Key (while a level is a work item), Total, Billable (with a billable rule), Amount (with rates), Cost and Margin (for the people who see them), % used (with budget columns), then Original estimate, Logged (all time) and Logged %, Remaining and Remaining % while their columns are picked. The two with a percent follow the lozenges: Remaining % puts the work that ends furthest past its estimate first. A row that holds work items goes by its highest, then by how many are over. Name opens ascending and the others largest first; the direction button flips it. The order is saved with the report and is not in the gadget, which keeps its rows in order of hours.
Filter
Use Filter to keep only the worklogs whose comment, work item or author holds the text; with a billable rule, Billable only keeps the worklogs on billable work items. Space keeps the time logged in one space; it shows when the worklogs come from more than one space. The timesheet adds up just those, and the line beside them says how many: “12 of 116 worklogs · 23h 30m”. The total at the top stays the whole report’s. The filter is the Worklogs view’s too, so switching views keeps it.
Expected hours
With people as rows (or people under Jira groups), the Expected toggle above the timesheet adds Expected and Against expected after Total. Expected is the working days of the period before today times the working-day length in Logline settings, such as 40h for a past Monday-to-Friday week of 8-hour days, plus what the person has logged today, up to one working day: the hours a full timesheet would hold so far. A day that is not over counts neither against anyone at nine in the morning nor for them at five. Against expected says how far each person is from it, in words: “40h under” in yellow, or “127h over”. Holidays and leave are not known to Logline. The totals row adds up Expected and leaves the difference empty. Without people as rows, there is no Expected toggle. The export carries both once per person, the difference as a signed number (“Against expected (h)”), and its totals row adds up both.
When you limit a report to chosen people or a Jira group and choose Show report, with people as rows, Expected switches on, once, and so do Gaps, the columns turning to days where the period allows: that is a team’s timesheet. With Everyone, a person who logged nothing in the period is not listed; the report says so while Gaps or Expected is on, with Choose people.
Show worklogs
The arrow at the start of a bottom-level row lists that row’s worklogs under it: date, author, work item, hours and comment. A line leaves out what its rows already say: under a work item, no work item; under a person, no author.
The worklogs behind a figure
Choose any figure in the timesheet, a day on a person’s row, a row’s Total or Billable, or a figure in the totals row, to list the worklogs it adds up: date and time, author, work item, hours and comment, newest first. The list is titled with the row and the column, such as “Ana Ruiz · Wed 7 Oct”, and counts exactly what the figure counts: the row’s values at both levels, the column’s days in the report’s time zone and, in the totals row, a worklog under two rows once. Hover over a figure to see how many worklogs are behind it. An empty day opens nothing. The list comes from the report already on screen, so it opens at once, without reading Jira again.
Limits
A report reads at most 10,000 work items and 50,000 worklogs. Over that, Logline says so and asks for a shorter period, fewer spaces or fewer people; it never shows a partial total. A big report is read in steps, with a progress bar, each step well inside Forge’s time limit for one call.
Every Logline site shares one hourly allowance of Jira requests, so each person can build only so many fresh reports in an hour. Past that, a report they built in the last few minutes still shows, with a line saying when fresh ones are back; otherwise the page says when. A report already being read always finishes, the work item panel is not limited, and nobody else is affected.
Names have an hourly allowance of their own, enough to open a 100-person timesheet about 25 times. Past it, for the rest of the hour, rows are in order of hours logged, the filter and the Author sort leave names out, and downloads wait; the report says for how many minutes.