[Sprint 2 - Task 4] Coordinator Approval & Rejection with Email Notifications + Logging

[Kamal-Poshala]

✨ Summary

This pull request implements Task 4 from Sprint 2 for Team A:

• ✅ Adapted approval and rejection functionality from the supervisor dashboard
• ✅ Integrated confirmation dialogs and required rejection reason (via prompt)
• ✅ Triggered email notifications to:
  • Student (ouEmail)
  • Academic Advisor (academicAdvisor)
  • Coordinator (hardcoded: coordinator@ipms.edu)
• ✅ Logged all approvals and rejections in server/logs/coordinatorActions.log

---

🛠️ Implementation Highlights

• Replaced dummy request logic with MongoDB integration using usertokenrequests collection
• Updated backend endpoints:
  • POST /api/coordinator/requests/:id/approve
  • POST /api/coordinator/requests/:id/reject
• Used existing emailService.js to handle outgoing notifications
• Created a new log file to track all coordinator actions

---

🧪 Testing

• Tested both approval and rejection flows with:
  • Local MongoDB data
  • Valid email .env configuration
• Verified log file updates and email success responses
• Checked error handling for invalid IDs and empty rejection reasons

---

📂 Files Modified

• server/routes/coordinator.js
• client/src/pages/CoordinatorDashboard.js
• server/logs/coordinatorActions.log

---

📌 Notes

• Coordinator email is currently hardcoded (coordinator@ipms.edu)

---

Ready for review and merge into team-a/development branch ✅

[Kamal-Poshala]

i will update this branch with latest changes. i didn't notice as the changes were made just yesterday.