Aayush taking over for Vamsi krishna creates a stacked horizontal bar graph for tools stoppage reason

[vamsikrishna1704]

Description

Related PRS (if any):

This backend PR is related to the 3780 frontend PR.
…

Main changes explained:

• Create bmToolsStoppageReasonController.js file for defining the functions to fetch unique projects and tools details.
• Create bmToolsStoppageReasonRouter.js file to map the uri to associated controller function.
• Create buildingToolStoppage.js file to define the schema model in DB.
  …

How to test:

1. check into current branch
2. do npm install and npm run build then npm start to run this PR locally
3. Clear site data/cache
4. log as admin user
5. go to dashboard→ Reports→ Total Construction Summary→Tools and Equipment Tracking.
6. verify filters to see appropriate results.

Screenshots or videos of changes:

ReasonOfStoppageOfTools-walkthrough.mp4

[beblicarl]

Tested the frontend of this and approved it because everything works as intended

https://www.loom.com/share/f7064847b0e6449490b6c5c527584057

[laynet]

I can't test this through the local host because the frontend branch can't be resolved, I submitted a review for that OneCommunityGlobal/HighestGoodNetworkApp#3780 (review)

[MeronTeweldebrhan]

PR Review Feedback

Testing Outcome

✅ Verified Tools and Equipment Tracking Card under Dashboard → Reports → Total Construction Summary.
✅ Proportion of Tools/Equipment filter works as expected.
✅ Tools by Availability chart functions correctly.
✅ Dark mode verified.
❌ Reason of Stoppage of Tools fails to load, showing: “Failed to load projects. Please try again.”

Suggestion
In the Proportion of Tools/Equipment filter, after selecting a project, switching directly to another project doesn’t refresh the list unless “All” is clicked first. Improving this behavior would enhance user experience.

[vamsikrishna1704]

Hi @laynet & @MeronTeweldebrhan, the problems you are facing is due to the recent node upgrade. I have resolved the node upgrade conflicts. Try to check the changes which address the errors you are facing. Thank you.

[dunstanad]

I tested the backend using frontend #3780 but the code didn't work as expected.

[sanjeev29]

Tested the changes with the related frontend PR - 3780. The filters and bar graph works as expected.

[sumedhkumar96]

Pulled the backend code and tested it along with the frontend locally, and functionalities are working as described by the dev. Screenshots are pinned in the frontend PR-3780

I have resolved the fetch error due to recent node upgrade.

[apoorvajainrp21]

the projects are not loading:

[Vinay944924]

Hi Vamsi,
I tested the PR locally and given the explanation in the frontend PR

[Sriamshreddy000]

Tested this PR along with the related frontend PR #3780.
Left detailed feedback and screenshots in the frontend PR for reference.

[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

[DeepighaJ]

I tested the PR locally and given the feedback in the frontend PR 4508