Leave Request List

Summary

The shared Leave route displays request history for employees and a wider request table for the legacy/admin rendering.

Employees, managers, HR administrators, QA, support, and frontend developers.

Purpose: review Leave requests and their current status.
Navigation: Leave, Team Leaves, or Leave Requests → /leave.
Preconditions: authenticated tenant user with the Leave route available.
Columns: ESS shows type, from date, to date, and status. The broader table shows employee, manager, type, date range, days, status, and actions.
Filters: the broader table filters by All, Pending, Approved, Rejected, or Cancelled. No source-backed search, date filter, or pagination exists.
Actions: View is present; eligible rows may show Cancel, Approve, and Reject.
Scope: employee rendering is self-oriented. Admin rendering uses all loaded requests. Team authorization semantics require confirmation.
Loading/empty/error: ESS has a skeleton and shared empty state. The broader page refreshes after actions and renders load/action errors. ESS request-page error display is a known gap.
API dependencies: ESS gateway request listing and compatibility request listing; see Leave API.
Screenshot placeholder: sanitized request list at desktop and narrow widths; remove names, dates, reasons, and balances.

Sorting is not explicitly implemented. Row details open a modal rather than a new route.

Requirement	Confirmed behavior
Purpose	Review employee or administratively visible Leave requests and current status.
Navigation path	Leave, Team Leaves, or Leave Requests → `/leave`.
Intended users	Employees and confirmed manager/admin menu audiences; final team scope requires confirmation.
Preconditions	Authenticated tenant user with the Leave route available.
Main components	`EssLeavePage`, `LeaveManagementPage`, shared request table and status badge.
Fields, columns, or sections	ESS: type, from, to, status. Broader view: employee, manager, type, dates, days, status, actions.
Filters	Status filter in the broader view; no search or date filter.
Actions	View, and conditionally Cancel, Approve, or Reject.
Validation	Action visibility is status/context based; server rules remain authoritative.
Loading state	ESS skeleton; no distinct legacy table skeleton.
Empty state	Shared ESS empty state or an empty broader table.
Success state	Refreshed rows/status after successful action.
Error state	Page-level legacy error; ESS query-error presentation gap.
Permission behavior	Route guard plus local scope/action checks; API enforcement is authoritative.
API dependencies	ESS gateway listing or compatibility request listing.
Related business rules	Self/team/admin scope and status transitions; see Business documentation.
Screenshot placeholder	Sanitized list at desktop and narrow widths with names, dates, reasons, and balances removed.