Timesheet Reports let you review logged hours by user, project, or custom grouping, and compare them against required or planned capacity. For the submission and approval workflow, see Timesheets Approval.

Toolbar & Filters Back to top

Every Timesheets view shares the same toolbar at the top — controls work identically across all sub-views.

Timesheet toolbar showing period picker, Day/Week/Month scope selector, Team/Users and Jira filter pickers, Projects, Worklog Type, and Export button
  • Period — eight presets (Current / Previous Week, Month, Quarter, Year) plus a custom date range. Use ← / → to step one period at a time; Today jumps back to the period containing the current date.
  • Day / Week / Month — sets column granularity across the whole table. Day shows one column per calendar day (weekends highlighted); Week and Month aggregate totals into broader buckets.
  • Team / Users or Jira Filter — two mutually exclusive row scopes. Team/Users lets you pick individuals or whole teams. Jira Filter scopes to worklogs on issues matched by a saved Jira filter — when active, allocation entries are hidden and the Worklog Type picker disappears.
  • Projects — narrows results to specific Jira projects, in addition to whichever scope is active above.
  • Worklog Type — toggle between Issue worklogs, Allocation worklogs, or Both (default). Hidden when a Jira Filter is active.
  • Active filter chips appear below the toolbar for every active selection. Clear all resets all filters at once.
  • Export Excel — downloads the full visible timesheet as a formatted spreadsheet with color coding, frozen headers, and native row grouping for hierarchical views.

Clicking a cell

Click any cell to open a detail dialog showing everything logged (and taken as leave) for that person on that date. At the top you see Capacity (daily required hours) and Logged (total hours logged). Below that, entries are listed per date in this order:

  • Leave entries — shown first with a red LEAVE badge, the leave type name (e.g. Vacation, Sick Leave), and duration (Full day or partial hours). Only approved leaves are shown.
  • Worklog entries — grouped by issue, each showing the issue key, summary, hours, author, and description.

If someone both took leave and logged work on the same day, the cell is highlighted as a conflict and the dialog surfaces both so you can review the overlap. An Export Excel button lets you download the entries shown.

Cell detail dialog showing Capacity 8h, Logged 2.25h, and one worklog entry on API-603 with author and hours

Cell Colors Back to top

In User Timesheets and Custom Timesheets (when grouped by Worklog Author), each cell on a user row is tinted based on the ratio of logged hours to that person’s available capacity. The same palette is used in Progress Reports and the Resource Scheduler, so the meaning is consistent across the whole plugin.

Color Logged / Capacity Meaning
Light Blue < 50% Underloaded — significant spare capacity
Yellow-Green 50 – 80% Moderate load — partially loaded, room for more
Green 80 – 100% On track — healthy target utilization
Yellow 100 – 120% Near overload — logged more than available capacity
Red > 120% Overloaded — or work logged on a leave / holiday day (Day scope only)
Blue Approved leave day with no logged work (Day scope only)
Orange Public holiday with no logged work (Day scope only)
Note: The blue and orange leave/holiday tints are only visible in Day scope — weekly and monthly columns aggregate multiple days so per-day tints are not applied.

User & Project Timesheets Back to top

User Timesheets Summary view showing logged hours per person across a period

User Timesheets shows logged hours from each person’s perspective, with three sub-views selectable from the left sidebar:

  • Summary — one row per person with total hours per period column.
  • By Project — expandable Person → Project tree; click a person row to see their hours split by project.
  • By Item — Person → Issue / Allocation breakdown with worklog descriptions visible per entry.

Project Timesheets shows the same data from the project side:

  • Summary — one row per Jira project with total hours logged across the period.
  • By User — expandable Project → Person tree showing each contributor’s hours.

Detailed Timesheet Back to top

The Detailed Timesheet shows every worklog as its own row in a flat table — useful when you need to audit, search, or export individual entries rather than see aggregated totals. Unlike the timeline views, there are no date columns; each row stands alone with its own date, user, project, issue, hours, and description.

Detailed Timesheet showing individual worklog rows with Group By Project, sortable columns, Include leave checkbox, and grand total
  • Group By — optionally group rows by any single Jira field (e.g. Project, User, Issue Type). Each group shows a subtotal. Leave the field empty for a flat unsorted list.
  • Columns — choose which columns to display. Available fields include Date, User, Project, Issue, Hours, Description, Issue Key, Worklog Type, Issue Type, Start Date, and Change Type.
  • Include leave — checkbox to show approved leave entries alongside worklogs. Leave rows display the leave type with a red LEAVE badge; partial-day leaves show the hours per day (e.g. 1h/day).
  • Sorted By — click any column header to sort; the active sort is shown as a chip above the table and can be cleared.
  • Grand Total — a pinned row at the bottom sums all hours in the current view.
Tip: Use Export Excel from this view when you need a full audit trail — every row exports exactly as shown, including the grouping, column selection, and leave entries.

Progress Reports Back to top

Three dedicated reports each compare hours across two dimensions. Cells are color-coded: blue = under capacity, green = on track, yellow / red = over capacity.

Timesheet Progress — Required vs. Logged

Compares how many hours each person was expected to work (their required capacity) against how many hours they actually logged. Use it to check whether timesheets are being filled in fully.

Timesheet Progress report comparing required hours versus logged hours per user

Resource Utilization — Required vs. Planned

Compares required capacity against planned work (original estimates distributed across working days, plus allocations). Use it to spot overbooking before the work begins — if someone exceeds 100%, their planned workload is more than their available hours.

Resource Utilization report comparing required hours versus planned capacity per user

Planned vs. Actual — Planned vs. Logged

Compares what was planned against what was actually logged. Run this after a sprint or period end to see whether estimates held up — if logged hours consistently exceed planned, your team may be underestimating.

Planned vs Actual report comparing planned hours versus logged hours per user

Display modes

All three Progress reports share five display modes — switch using the segmented control above the table. The data is identical; only the visual density changes.

Progress display mode selector showing Bar, Per Day, Heatmap, Stacked, and Totals Only options
  • Bar — a progress bar per row showing the overall ratio at a glance.
  • Per Day — inline values per column: numerator / denominator with a signed delta (e.g. 13/8 +5).
  • Heatmap — color-coded cell backgrounds with only the delta shown; ideal for scanning many people at once.
  • Stacked — numerator and denominator stacked vertically in each cell.
  • Totals Only — hides per-day columns and shows only the period summary totals.

In Per Day, Heatmap, and Stacked modes, hover over any day cell to see a tooltip with the full breakdown — both values, the delta, and the percentage of target (e.g. Logged Hours: 13 / Required Hours: 8 (Δ +5, 163% of target)).

Progress cell tooltip showing Logged Hours: 13 / Required Hours: 8, delta +5, 163% of target

Custom Timesheets Back to top

Custom Timesheets grouping configuration showing field level selectors

Custom Timesheets work the same way as User & Project Timesheets — the same toolbar, filters, period picker, and clickable cells — but instead of fixed groupings you define your own hierarchy using any Jira field. This lets you build deeper, more specific breakdowns that the standard views don't offer.

You can stack up to 5 levels. For example: Worklog Author → Project → Epic → Issue Type gives you a per-person view broken down all the way to issue type — something neither User nor Project Timesheets can show alone. Items with no value for the selected field are grouped under “(No value)”.

When Worklog Author (or Assignee) is the top-level grouping, date cells get the same workload color coding as User Timesheets — blue through green to red based on logged hours vs. capacity. Deeper nesting levels always show plain hour totals.

Who sees whose timesheets Back to top

Timesheets are sensitive personal data, so visibility is stricter than elsewhere in the plugin. Regular users see only their own hours; team managers and approvers see their assigned team members; admins see everyone. The full access rules are in Permissions › Who Sees Whose Timesheets.

Note: Sharing a team with a colleague lets you see their assigned issues on the Scheduler, but not their timesheet or worklogs — you need explicit approver, viewer, or manager access for that.

Need Help?

If you have questions about timesheets or need help with your setup, our support team is here to help.

Contact Support