Change OOO flow from user status page to requests flow.

[Dhirenderchoudhary]

Overview

The OOO feature is being migrated from the user details/status page so that it requires approval to the requests module. This change improves the admin experience by making OOO status actionable rather than read-only.

• Current Problem: OOO is in the user details page.
• Actionable: Allow admins to approve/reject OOO requests directly.
• Consistency: All requests flow through the same interface for admin.

Scope

• Remove /users/details/ module.
• Remove OOO constants from /users/constants.js
• Remove availability filter from /users/index.html and /users/script.js
• Leverage existing /requests/script.js which already supports OOO requests.

Current Behavior

Users: Can directly set their own OOO status (no approval needed).
Admins: Can only view/see the OOO status (only sees).

1. User navigates to Users module.
2. Clicks on their profile.
3. Sees Availability option ccordion showing:
   • Status (ACTIVE, IDLE, OOO)
   • Last update time
   • Status message
4. No action possible by admin - purely informational to admin that a user is on OOO.

Technical Implementation

• Location: /users/details/ directory.
• API Call: GET /users/status/{id} from backend.

Changed Behavior

Users: Submit an OOO request (asking for permission to go OOO).
Admins: Review and approve/reject the OOO request.
Approval Process: OOO status is only active after admin approval.

1. User navigates to Requests module.
2. Clicks on the OOO tab (among Extension, Onboarding tabs)
3. Sees all OOO requests with details:
   • User who submitted the request
   • OOO duration (start/end dates)
   • Reason/message
4. Can take action - Approve or Reject the request

Technical Implementation

• Location: /requests/script.js.
• API Call: GET /requests?type=OOO from backend.

Key Change
From: Users set OOO directly.
To: Users request OOO → Admins approve/reject.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

RealDevSquad/website-www#1070 - fix: update request body for create ooo requests in dev mode [closed]
RealDevSquad/website-backend#2466 - refactor: OOO request schema for requestedBy and userID field [closed]
#1024 - fix(#1020): fix ooo accept/reject flow [merged]

👤 Suggested Assignees

• MayankBansal12
• RishiChaubey31
• Hariom01010

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!