The following applies to End User (internal user / client user) in which currently the Queue Item Defer date/time displaying in a format yyyy-mm-dd and make this configurable
Supporting Actors could be
Browser (Chrome, Edge, Firefox)
Operating System Locale
Web Application UI Layer
Goal
Allow users to view dates in their preferred format (dd‑mm‑yyyy or mm‑dd‑yyyy) within the web application UI to reduce confusion, misinterpretation, and data-entry errors.
Problem Statement
Dates displayed in web applications are often rendered according to the browser or OS locale, not the user’s explicit preference. This can cause ambiguity and errors, especially in international environments where both US (mm‑dd‑yyyy) and EU (dd‑mm‑yyyy) formats are used.
Example:
04‑05‑2026
US user interprets: April 5, 2026 (mm-dd-yyyy)
EU user interprets: 5 May 2026 (dd-mm-yyyy)
Functional Requirements
FR1 – User Preference
The application shall allow users to select a preferred date format:
dd‑mm‑yyyy
mm‑dd‑yyyy
FR2 – UI Rendering
All dates displayed in the UI (lists, tables, detail views) shall respect the selected date format.
Formatting is handled at the UI layer, independent of browser default locale.
FR3 – Input Handling
Date input controls must accept user input consistent with the selected format.
Non‑Functional Requirements
Consistency: Same date format across the entire application.
Accessibility: Date format clearly visible and predictable.
Internationalization: Decoupled from browser or OS language settings.
Auditability: Backend data remains locale‑neutral (ISO format).
Main Flow
User opens Profile / Preferences.
User selects preferred date format (dd‑mm‑yyyy or mm‑dd‑yyyy).
Preference is saved.
UI re-renders all visible dates using selected format.
All subsequent sessions respect the stored preference.
Alternate Flows
A1 – No Preference Set
System defaults to:
Browser locale or
Organization-wide default (e.g. dd‑mm‑yyyy for EU tenants)
... View more