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.

Reports Overview — Report Gallery

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.

Report Templates

Each report template is shown as a visual card with an illustration and brief description. Select a template to open the configuration dialog, where you set the date range, scope, grouping, and filters before generating the report.

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.

Utilization Forecast Report

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.

Grouping Options

  • None — flat list of users with their utilization totals.
  • Project — users grouped under each Jira project they are assigned to, with per-project utilization breakdown.
  • Issue — users grouped under individual issues, showing remaining hours per issue.
Important: This report uses remaining estimate mode. Only hours remaining on in-progress or to-do issues are counted. Completed issues contribute zero hours. If an issue has no remaining estimate set in Jira, it is excluded from the calculation.

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.

Project Resources Report

How It Works

  • Each Jira project with scheduled issues appears as a collapsible row.
  • Expanding a project row reveals individual team members assigned to issues within that project.
  • Hours shown represent the remaining estimate for each person within the project, distributed across the selected period's working days.
  • Date columns reflect the configured scope (day, week, or month).

Use Case

Use this report to understand how your team's effort is spread across projects. Identify projects that are consuming more resources than planned, or find team members who may be stretched across too many projects simultaneously.

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.

Leave Report

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.
Note: Only approved leave requests are included in this report. Pending, rejected, and recalled requests are excluded.

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.

Worklog Report

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.

Filtering

Use the configuration dialog's filter options to narrow the worklog report to specific users, projects, or date ranges. This is useful for generating focused time reports for client billing, sprint reviews, or individual performance tracking.

Planned vs Actual Back to top

The Planned vs Actual report compares the Original Estimate (planned hours from the Jira estimate field) with Time Spent (sum of worklogs for the selected period). It calculates remaining effort and deviation so you can see where projects are on track, over budget, or under-logged.

Planned vs Actual Report

Two Views

  • By Issue — each row is an individual Jira issue, grouped by project with per-project summary rows.
  • By Project — each row is a Jira project, aggregating all issues into totals for a high-level overview.

Key Columns (By Issue View)

Column What it shows
Issue Key The Jira issue key (e.g., WH-123)
Issue Summary The issue title
Assignee People assigned to the issue
Start / End Timeline dates from the mapped date fields
Original Estimate Planned hours from Jira's estimate field
Time Spent Sum of worklogs for this issue within the selected period
Remaining Original Estimate minus Time Spent (minimum 0)
Deviation Time Spent minus Original Estimate. Positive = over budget
Deviation % (Deviation / Original Estimate) × 100

Deviation Color Coding

  • Red — Over budget (Time Spent exceeds estimate)
  • Green — On track (within 20% of estimate)
  • Yellow — Under-logged (large gap between estimate and actual)
  • Gray — No data (no estimate or time spent)

Use Cases

  • Sprint retrospectives — compare planned vs actual across a sprint.
  • Budget tracking — spot issues where actual hours far exceed estimates.
  • Team calibration — identify who consistently over- or under-estimates.
Note: This report uses original estimates and raw worklogs. It does not use the remaining estimate calculation from the workload indicator. The "Remaining" column here is simply Original Estimate minus Time Spent.

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:

Report Period Scope Grouping Filters
Utilization Forecast This Week, Next Week, This Month, Next Month, Custom Day, Week, Month None, Team, Project, Item Teams, People, Projects
Project Resources This Week, Next Week, This Month, Next Month, Custom Day, Week, Month Project (fixed) Projects
Leave Report This Month, Last Month, This Quarter, Last Quarter, This Year, Custom None, Team Teams, People
Worklog Report Today, This Week, Last Week, This Month, Last Month, Custom None, Team Teams, People
Planned vs Actual Today, This Week, Last Week, This Month, Last Month, Custom Project (fixed) Projects
Note: When Custom period is selected, date-from and date-to fields appear so you can specify an exact date range. The “—” in the Scope column means that report does not have a time-column granularity option.

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.

Tip

Create bookmarks for recurring reports such as weekly utilization checks or monthly leave summaries. This saves time and ensures consistency when reviewing the same metrics across periods.

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.

Tip

Use the exported Excel file to build custom charts, share utilization summaries with management, or compare planned vs. actual hours in your own spreadsheet workflows.

Need Help?

If you have questions or need assistance, our support team is here to help.

Contact Support