Casstiel improve weekly project summary filters and section usability#5415
Draft
CasstielP wants to merge 11 commits into
Draft
Casstiel improve weekly project summary filters and section usability#5415CasstielP wants to merge 11 commits into
CasstielP wants to merge 11 commits into
Conversation
…ve_weekly_project_summary_filters_and_section_usability
…ve_weekly_project_summary_filters_and_section_usability
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
CasstielP
marked this pull request as ready for review
July 25, 2026 16:11
CasstielP
marked this pull request as draft
July 25, 2026 18:29
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implements the frontend portion of the Weekly Project Summary usability improvements. This PR improves the Weekly Project Summary page by adding clearer filter context, section controls, comparison UI structure, section-level badges, empty-state support, and loading feedback when filters change.
The task could not be fully completed with frontend changes alone because real comparison values, dynamic badge counts, and accurate no-data detection require backend support across related routes, controllers, models, and chart-specific data sources. This PR adds the frontend structure needed for those features, while backend logic will be handled separately.
Fixes/Implements: Weekly Project Summary filter and section usability improvements
Related PRS (if any):
This frontend PR is related to the potential backend work for Weekly Project Summary data support. The backend PR is expected to provide real project/date filtering, previous-week comparison data, dynamic section counts, and no-data detection for dashboard sections.
…
Main changes explained:
…
How to test:
Check out this frontend branch.
Run the app locally with the normal frontend setup command.
Log in as an admin user.
Go to Reports -> Total Construction Summary
Verify the page shows the active project and selected week near the top.
Click Expand All and confirm all sections open.
Click Collapse All and confirm all sections close.
Enable Compare with Previous Week and confirm comparison banners appear inside opened sections.
Confirm the Project Status cards and charts are not squeezed or compressed when comparison mode is enabled.
Verify the section badges appear in the section headers.
Change the available project/date filters and confirm the loading feedback appears.
Test in dark mode and confirm the controls, badges, comparison banners, and section headers remain readable.
Use Share PDF and confirm the export still works without including the frontend-only controls.
Screenshots or videos of changes:
Screen.Recording.2026-07-24.at.9.22.43.PM.mov
Note:
This PR adds the frontend structure for the task requirements, but some values are still frontend-driven placeholders. Real comparison messages, dynamic badge counts, and accurate no-data states require backend support. Backend implementation has started separately, beginning with the /issues/breakdown route so the Issues Breakdown chart can retrieve authorized JSON data and render from the backend endpoint.