Reports

Overview Back to top

The Reports module provides five ready-made report templates designed to give managers and team leads clear visibility into resource utilization, project effort distribution, leave patterns, time entry details, and planned-vs-actual comparisons. Reports are accessed from the Reports view in the main navigation.

The Reports view is organized into two tabs:

• Report Templates — a card-based gallery showing the five available report types. Click any card to open the configuration dialog and generate the report.
• Bookmarked Reports — saved report configurations that you can re-run with a single click, without re-entering parameters each time.

Utilization Forecast Back to top

The Utilization Forecast report shows per-person remaining workload from today forward. It compares each team member's available capacity against their remaining scheduled work to calculate a utilization rate.

Columns

• Person — the team member's name and avatar.
• Total Available — the total available working hours within the selected period, based on their capacity scheme and excluding holidays and approved leave.
• Utilized — total remaining estimate hours distributed across working days from today forward. Done issues contribute 0 hours. Uses the Jira remaining estimate field.
• Rate (%) — utilization percentage calculated as Utilized / Total Available × 100.

Row Tiers

Results are rendered in up to four nested tiers:

• Grand total — sum across all users in scope. Hidden when only one team is shown (the team summary already covers it).
• Team summary — one row per team aggregating its users. Users not on any selected team appear under a synthetic Without Team group.
• User row — per-person totals and per-day cells.
• Grouping children — only when Group by is set to Project, Epic, or Issue (see below). Each child row shows the user's utilization for one project / epic / issue.

Group by

Adds an extra row tier under each user, splitting their utilization by where the work is going. The percentage on a child row divides the child's hours by the user's total capacity, so child percentages can sum to less than 100% (the rest is uncategorized capacity, leave, or holidays).

• None — flat user rows, no per-grouping breakdown.
• Project — one child row per Jira project the user has work on, labeled [KEY] Project Name.
• Epic — one child row per epic, labeled [ISSUE-KEY] Epic summary. Sub-tasks of stories without an epic link bucket under Without Epic.
• Issue — one child row per issue, labeled [KEY] Summary.

Allocations whose target matches the chosen grouping (PROJECT-target with Project, EPIC-target with Epic, ISSUE-target with Issue) appear in their own row with a (allocation) suffix so you can tell allocated time apart from the project's direct issue work. Custom-category allocations always show as Custom: <name> regardless of group mode.

Display per-day cells as

• Hours (default) — each per-day cell shows scheduled hours.
• Percentage — each cell shows scheduled / effective capacity × 100, where effective capacity is the day's working hours minus any leave. Cells on weekends, holidays, or days fully consumed by leave stay blank in either mode. Summary columns (Total Available, Utilized, Rate) always remain in hours / percentage as appropriate.

Include allocations

Checkbox, default on. When checked, allocations contribute to scheduled hours and (with grouping) to per-grouping rows. Uncheck to see only work scheduled via Jira issues, ignoring all allocation bookings.

Project Resources Back to top

The Project Resources report shows remaining effort distributed across your Jira projects. Each project is displayed as a top-level row, with per-person sub-rows showing how the remaining work breaks down by team member.

How It Works

• Each Jira project with scheduled issues or allocations appears as a top-level row.
• Each project expands into per-person sub-rows showing how that project's hours break down by team member.
• Hours shown represent the remaining estimate for each person within the project, distributed across the selected period's working days, plus any allocation bookings (see Include allocations below).
• Date columns reflect the configured scope (day, week, or month).

Include allocations

Checkbox, default on. When checked, allocation bookings contribute to project hours alongside the remaining-estimate distribution from Jira issues. PROJECT-target allocations bucket under that project; ISSUE-target and EPIC-target allocations bucket under the issue's project. Uncheck to see project hours from Jira issues only — projects that have only allocations (no scheduled issues) will not appear when this is unchecked.

Leave Report Back to top

The Leave Report provides a summary of approved leave days per person within the selected period. It breaks down time off by leave type so you can see how different categories of absence impact team availability.

Columns

• Person — the team member's name and avatar.
• Total — total number of approved leave days in the period.
• Holidays — public holidays from assigned holiday calendars that fall within the period.
• Leave type columns — one column per configured leave type (e.g., Vacation, Sick Leave, Personal, Parental), showing the number of days taken for each type.
• Date columns — columns for each date period (day, week, or month depending on scope), showing leave days per period.

Worklog Report Back to top

The Worklog Report displays every worklog entry within the selected period as an audit trail. It provides a detailed view of who logged time, on which issues, and how much.

Columns

• Status — the timesheet approval status for the worklog's period (only shown when timesheet approval is enabled in Settings).
• Person — the user who logged the time entry.
• Date — the date the work was performed.
• Project — the Jira project the issue belongs to.
• Issue Key — the Jira issue key (e.g., WH-42).
• Issue Summary — the issue title/summary text.
• Time Spent — hours logged in the worklog entry.
• Comment — optional description entered with the worklog.

Planned vs Actual Back to top

The Planned vs Actual report tracks each issue’s Original Estimate against the Time Spent and Remaining Estimate stored on the issue in Jira. It computes a deviation and a status verdict (on track, under-estimated, or over-estimated) per issue and per project, so you can see where the original plan still holds and where reality has diverged.

Two Views

• By Issue — each row is an individual Jira issue, grouped by project with a per-project summary row that sums the project’s issues.
• By Project — project rollup rows only, hiding the per-issue breakdown for a high-level overview.

Columns

Status

The Status badge measures whether the original plan still holds, not whether work has been completed. It is set per issue and recomputed for each project rollup from the summed totals.

• ON TRACK — Time Spent + Remaining equals the Original Estimate (within a 2-minute tolerance). The plan still matches the current commitment, even if work is only partly done.
• UNDERESTIMATED — Time Spent + Remaining exceeds the Original Estimate. The team now expects to need more time than originally planned. Also applies when work was logged on an issue with no original estimate.
• OVERESTIMATED — Time Spent + Remaining is below the Original Estimate. The plan was larger than what is actually needed.

Project Rollup

Project subtotals and the grand total are computed by summing each issue’s Original Estimate, Time Spent, and Remaining Estimate — then applying the same Deviation and Status formulas to those sums. A project with one underestimated issue (+1h) and one overestimated issue (−1h) will roll up to ON TRACK, since the totals net out.

Use Cases

• Sprint retrospectives — identify which issues drifted from their original estimate and why.
• Estimate calibration — spot teams or individuals who consistently under- or over-estimate; the status badges aggregate cleanly at the project level.
• Forecast vs commitment tracking — see at a glance whether the current commitment (Spent + Remaining) is creeping past the originally agreed plan.

Creating Reports Back to top

To generate a report, click a template card from the gallery. A configuration dialog opens with options specific to that report type. Fill in the parameters and click Generate.

Each report type has a different set of configuration options:

Bookmarking Reports Back to top

Save frequently used report configurations as bookmarks so you can re-run them without re-entering parameters each time. Bookmarks remember the report type, date range, scope, grouping, and all filter settings.

1. Generate a report using the steps above.
2. Click "Save as Bookmark" in the report toolbar.
3. Enter a name for the bookmark (e.g., "Weekly Team Utilization" or "Q2 Leave Summary").
4. Click "Save" — the bookmark appears in the Bookmarked Reports tab on the Reports view.

To re-run a bookmarked report, switch to the Bookmarked Reports tab and click the bookmark card. The report generates immediately using the saved configuration. You can also delete bookmarks you no longer need.

Exporting to Excel Back to top

Any generated report can be exported to an Excel spreadsheet for offline analysis, sharing with stakeholders, or archiving.

1. Generate a report using any of the five report templates.
2. Click "Export to Excel" in the report toolbar.
3. An .xlsx file is downloaded to your computer containing the same data shown in the report view — all columns, rows, groupings, and totals are preserved.

Related Pages Back to top

• Resource Scheduler — the resource scheduler where issues are visualized and planned.
• Settings & Configuration — configure capacity schemes, holidays, and feature toggles that affect report data.
• Permissions & Access — understand user roles and who can generate reports.