Dldss-422 -

| ID | As a… | I want to… | So that… | |----|-------|------------|----------| | DLDSS‑422‑01 | End‑user | Export my transaction history as a CSV | I can analyze the data in Excel | | DLDSS‑422‑02 | Admin | Configure which columns are included in the export | I can control data exposure | | DLDSS‑422‑03 | Support agent | View export logs | I can audit usage for compliance |

Add additional stories for edge cases, permissions, error handling, etc. dldss-422


  • Durability: configurable commit-to-flush semantics. Default: synchronous replication to R nodes and durable append to at least one NVMe before acknowledging write.
  • Tail-latency control: per-node admission control, backpressure to clients, and prioritized compaction to avoid stalls.
  • | # | Condition | Testable Outcome | |---|-----------|------------------| | 1 | Visibility – The “Export CSV” button appears directly above the results table only when at least one row is displayed. | UI shows the button in all search result views with ≥1 row; hidden otherwise. | | 2 | One‑Click Export – Clicking the button triggers an immediate CSV download without opening any modal or additional UI. | File download starts within 2 seconds of click. | | 3 | Column Order – The exported CSV respects the current column ordering displayed in the UI (including any hidden columns). | CSV column headers match the order shown on screen; hidden columns are omitted. | | 4 | Data Fidelity – All rows currently displayed (including pagination) are included in the CSV. | If 200 rows are shown across 4 pages, the CSV contains 200 rows (excluding header). | | 5 | Filename Convention – The file is named search-results-YYYYMMDD-HHMMSS.csv. | Example: search-results-20260411-143025.csv. | | 6 | Performance – Export of up to 5 000 rows completes in ≤ 5 seconds on a typical production environment. | Load test with 5 000 rows passes timing requirement. | | 7 | Permission Check – Only users with the Export permission can see and use the button. | Users lacking the permission see no button; attempt to call the endpoint returns 403. | | 8 | Error Handling – If the export fails (e.g., server error, timeout), a non‑intrusive toast notification appears: “Export failed – please try again or contact support.” | Simulated server error returns toast; no file download is triggered. | | 9 | Accessibility – Button has an ARIA label “Export current results as CSV” and is reachable via keyboard (Tab → Space/Enter). | Screen‑reader reads the label; keyboard navigation works. | |10 | Documentation – The feature is documented in the user guide under “Exporting Search Results”. | New section appears with screenshot and description. | | ID | As a… | I want


    | Goal | Metric | Target | |------|--------|--------| | e.g., Increase self‑service | % of export requests handled without support | ≥ 90% | | Reduce time to obtain data | Avg. time to download CSV | ≤ 5 seconds | | … | … | … | Add additional stories for edge cases, permissions, error