Make formating consistent accross Resource Reports

[manuvarkey]

What problem does this solve

Currently, the Resource assignments report groups entries by resource, which provides clear visual separation between different resources.

The Resource loading per week report also groups entries by resource logically, but it is displayed using a plain table style. As a result, the visual layout does not clearly communicate the resource grouping.

What should the app do

The Resource loading per week report should use the same resource-grouped visual style as the Resource assignments report instead of a plain table layout.

Each resource should be visually separated as a group, with its corresponding weekly loading entries shown under it.

Anything else

[manuvarkey]

Further, it would be useful for the Resource loading report to support the following options:

1. Weekly / Monthly aggregation options.
   • Weekly — aggregate loading by week.
   • Monthly — aggregate loading by month.
2. A configurable reporting window, similar to the Window (weeks) option available in the Resource assignments report.

The reporting window may follow the selected aggregation period (for example, weeks for weekly aggregation and months for monthly aggregation). Alternately a common Reporting Period control shared with other reporting tools may be used.

These options would support both overall resource review, near-term resource planning, and longer-term capacity analysis.

[Nozzit]

Implemented in #134 (merged to main; the web build deploys automatically).

Resource loading now uses the same resource-grouped style as Resource assignments: the resource name and type appear only on the first row of each group, rows for that resource follow underneath — in the on-screen table and in the PDF export (both are drawn from the same column spec). The report is titled "Resource loading" instead of "… per week".

From your follow-up comment:

• Weekly / Monthly aggregation — new Aggregation option; monthly buckets are calendar months, using the same day-by-day distribution as the histogram on the Resources tab.
• Reporting window — the report follows the shared Reporting period control from Support more flexible Reporting Period Selection for Reports #120 (default: project duration); every calendar week or month that touches the period is included as a whole, so a row always shows the same number as the histogram.

Both resource reports now count "Resources" the same way (what is in the table) and share the same period subtitle.

One known limitation, documented in the in-app guide: when a page break in the PDF falls inside a group, the resource name is not repeated on the next page (this was already the case for the assignments report).

Thanks for the clear write-up — the screenshots and the note about a shared period control made this straightforward to scope.

---

Generated by Claude Code