Roshini Seelamsetty - (PRIORITY HIGH) Yagna: Hours Completed / Tasks Report – Data Accuracy Needs Review

[roshini1212]

Description

Related PRS (if any):

This backend PR is related to the #5000 frontend PR (roshini_feat_hours_chart_percentage_label).
To test this backend PR you need to checkout the (OneCommunityGlobal/HighestGoodNetworkApp#5000) frontend PR.

Main changes explained:

• Update src/helpers/overviewReportHelper.js to fix getTaskHours() to only count entries where taskId is a valid ObjectId, and fix getProjectHours() to exclude entries where taskId is already an ObjectId to prevent double-counting
• Update src/helpers/overviewReportHelper.js to fix hoursSubmittedToTasksPercentage calculation from taskHours / projectHours to taskHours / (taskHours + projectHours) * 100
• Update src/helpers/overviewReportHelper.js to add taskPercentage, projectPercentage, totalTangibleHours, and hoursDistributionLabel fields to the response for frontend consumption

How to test:

1. Check out roshini_fix_hours_completed_accuracy branch
2. Run npm install then npm start to run the backend locally
3. Clear site data/cache
4. Log in as Owner
5. Go to Reports → Hours Completed (Tasks view)
6. Set a historical date range with known data (e.g. Jan 2025 – Mar 2026)
7. Verify the Hours Completed header shows a reasonable percentage (not thousands of %)
8. Verify the API response includes hoursDistributionLabel in format "X% Tasks | Y% Projects (Total = 100%)"
9. Verify taskHours and projectHours in the API response are not double-counting the same entries

Screenshots or videos of changes:

Before:

After:

[sonarqubecloud]

Quality Gate passed

Issues
0 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

[Anusha-Gali]

Hi Roshini,

I have reviewed your PR locally and the API works as per requirement.