Saurabh taking over for Saicharan - Project status summary API for donut chart (backend)

[Saicharan1505]

Description

Implements Phase 2 Summary Dashboard: Project Status Donut Chart (Backend).
This feature provides an API endpoint /api/project-status/summary that aggregates Active, Completed, and Delayed projects, supporting date filters.
Implements # (Phase 2 Action Item)

Related PRS (if any):

This backend PR is related to the #4040 frontend PR.

Main changes explained:

• Created new projectStatus model for storing project status data.
• Implemented projectStatusService.js to aggregate counts and percentages.
• Added projectStatusController.js to handle requests with optional date filters.
• Created projectStatusRouter.js and registered it in routes.js.
• API returns total projects, counts by status, percentages, and applied date window.
• Tested endpoints in Postman for various date ranges.

How to test:

1. Check out the current branch (or)
   Check into this branch:
   git fetch origin feature/project-status-donut-backend
git checkout feature/project-status-donut-backend
2. Run npm install and npm run dev.
3. Use Postman to call:
   GET http://localhost:4500/api/project-status/summary
   • Without dates (returns all projects).
   • With ?startDate=YYYY-MM-DD&endDate=YYYY-MM-DD filters.
4. Verify API returns:
   • totalProjects
   • activeProjects, completedProjects, delayedProjects
   • percentages for each category
   • window with startDate and endDate.
5. Confirm frontend donut chart reflects the API response.

Screenshots or videos of changes:

Note:

• Reviewers should verify aggregation logic in projectStatusService.js.
• Double-check date filtering correctness.
• Ensure API response matches frontend requirements.

[akshith312]

Tested the PR locally. All the end points display the desired results.

project-status/summary:

With parameters:

[aditya2512]

The aggregation pipeline in projectStatus.service.js is well-designed efficiently grouping by project status and date range. The use of dayjs for robust date parsing and validation of both startDate and endDate parameters prevents edge case API misuse. Schema indexes on the project status fields are good for scale, especially with time windowed queries.
Error handling is granular, with informative responses for 400 (bad request) and 500 (internal error). Returning both count and percentage in the response is ideal for frontend integration, especially for chart generation (like a donut chart). Integration of the new route into the central router is clear and non-intrusive.
As a possible enhancement, adding API documentation (Swagger/OpenAPI or README) will further help frontend devs consume this endpoint. Recommend expanding test coverage with unit and integration tests for both controller and service logic to future proof any status logic changes.

[Prem203]

Checked the PR with an admin account and all the endpoints are working as expected.

[Aswin20010]

Reviewed PR #4040+1709 (Project Status Donut Chart Visualization). Verified proper integration with backend and correct rendering of the donut chart with Active, Completed, and Delayed project segments. Confirmed hover tooltips display accurate counts and percentages, and total project count appears at the chart center. Tested From/To date filters for functional accuracy and verified numeric data alignment in the right-side panel. Checked CSS module styling consistency and responsiveness. No functional or UI regressions found — approved the PR.

[Anusha-Gali]

Hi Juhitha,

I have reviewed your PR locally and the backend API calls work as per requirement.

[maithili20]

Hi @vamsidharpanithi
Left my comments at OneCommunityGlobal/HighestGoodNetworkApp#4040 (comment)

[Juhitha-Reddy]

Screen.Recording.2026-03-02.at.10.32.27.PM.mov

Resolved merge conflicts and tested locally. Please verify

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ManojPuttaswamy]

The function has no try/catch. If the aggregation fails, the error will propagate unhandled to the caller.

[SharadhaKasiviswanathan]

I have tested and reviewed this PR locally, also posted comments and screenshots on the frontend for PR #4040
OneCommunityGlobal/HighestGoodNetworkApp#4040 (comment)

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[handikaharianto]

Hi @Saicharan1505 , after reviewing your PR, I have concluded the following findings:

Requires some changes

Project summary data (without dates params) ❌

The response doesn't have the window property that includes startDate and endDate.

Project summary data (with dates params)❌

The response doesn't have the window property that includes startDate and endDate.

projectStatusService.js is not connected to projectStatusController.js

In the Note section that you wrote, you mentioned that we need to verify the aggregation logic in projectStatusService.js. However, you did not even use it and this file actually includes the window property that I mentioned earlier as missing.

For the frontend side, I couldn't confirm the frontend donut chart reflects the API response because the frontend side has errors that are not fixed yet. refer to: this link