Nikita weekly company summary email

[ArtemisNyx3]

Description

Related PRS (if any):

This frontend PR is related to the #1291backend PR.
…

Main changes explained:

• Added a Total Summary Email page under reports tab
• Updated Login.jsx to be helpful for puppeteer
• Updated AccordianWrapper.jsx to be helpful for puppeteer
  …

How to test:

1. check into current branch
2. do npm install and npm i to run this PR locally
3. Clear site data/cache
4. log as admin user
5. Follow Backend Steps
6. go to dashboard→ Tasks→ Total Org Summary Email
7. Enter your email address and verify if you are getting the screenshot of the 'Total Org Summary' Dashboard. The contents of the attachment are not in the scope of this PR,
   i. Verify if you are getting all the graphs in the email attachment
   ii. if they are loaded (This depends on the performance of your system. Feel free to increase timeout value in reportsController. js
   The timeout is set to 50 sec it should be adequate
   

Screenshots or videos of changes:

The email looks something like this

The attachment

Note:

I appreciate your patience 💖

[netlify]

✅ Deploy Preview for highestgoodnetwork-dev ready!

Name	Link
🔨 Latest commit	5b94b00
🔍 Latest deploy log	https://app.netlify.com/projects/highestgoodnetwork-dev/deploys/6934b788e1fc0d0008d3047e
😎 Deploy Preview	https://deploy-preview-3316--highestgoodnetwork-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[cgomezhub]

the function is general working but the subjt and message that is sending are diferents to the backend code

[Dharmik1710]

Reviewed the code changes for the Total Org Summary Email feature. The form structure, field validation, and submission logic are clearly implemented, and the flow integrates well with the existing dashboard components.

I was not able to test the end-to-end functionality due to the requirement of setting up a GCP account with billing details, but the frontend logic and UI implementation appear consistent with the intended behavior described in the PR.

The component looks well-structured and aligns with the expected admin workflow.

[naiduajaykumar]

I had followed every step what I understand in the description but it doesn't work for me. When I enter the recipient email its getting failed and getting 500 Error code. Can you please include testing steps clearly. Thank you.

[sonarqubecloud]

Quality Gate passed

Issues
6 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 Nikita,

I have tried to review your PR locally and did all the changes you have mentioned and even updated the REACT_FRONTEND_URL = http://localhost:5173 in backend env still have unable to receive an email. It keeps saying "Failed to send email." Do let me know if i am missing any step. I have added my email as recipient and have not touched any Puppeteer logic.

[DiyaWadhwani]

Hi, I was able to receive the email. For anyone else reviewing this PR, please ensure you update your 'const uri' to the latest in the below-mentioned files:
db.js, addMembersToTeams.js, addNewField.js

On the other hand, the total org summary in general doesn't work so the attachment in the email is of a 'Something went wrong' and the 'Refresh Page' button.
The rest works as expected. Attached video below.
https://github.com/user-attachments/assets/071d6edb-25be-438b-a78a-aad27f205713

Also added myself as a recipient and tried sending an email from the frontend. That works too.

Overall, the main functionality works but needs a lot of new updates in the code, since it is pretty old.

[DiyaWadhwani]

Created a new PR set with updated dev code changes - #2090; #4953