ZEVA 2 - Implement standardized Audit History view for system items
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 6
- Avg merge
- 14h 22m
- Merged PRs (30d)
- 32
Description
**Describe the task**
Implement a standardized Audit History view for items across the system.
This applies to system entities that contain historical activity, such as (but not limited to):
IDIR User
- MYR
- Legacy Reassessment
- Credit Applications/ Transfers/ Agreements
- Penalty Credits
- ZEV Models
BCEID User
- MYR
- Legacy Reassessment
- Supplementary reports
- Credit Applications/ Transfers/ Agreements
- ZEV Models
- other similar record types where history is available
The history view should be displayed as a separate tab within the item detail page (e.g. [Item Name / ID/ Number] and Audit History).
**This ticket is focused on the **visual** structure and reusable layout of the Audit History page only.**
The exact history content, labels, and displayed fields may vary depending on the item type and will be defined separately where needed.
**Prototype**
[Prototype](https://www.figma.com/proto/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?page-id=1413%3A12346&node-id=1896-8437&viewport=4614%2C-11442%2C0.33&t=MKynvR4NTXSMIr9C-1&scaling=scale-down-width&content-scaling=fixed&starting-point-node-id=1413%3A15301)
[Wireframe](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=1896-8437&t=kTFVEX0yKfNz0Eox-1)
**Purpose**
Create a consistent and reusable Audit History layout across the system for any item that contains historical records.
**Acceptance Criteria**
- [x] Items with history support an Audit History tab within the detail page.
- [x] The Audit History tab is displayed alongside the main item tab (e.g. item details / item ID tab).
- [x] The Audit History view visually follows the approved [design pattern.](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=1896-8437&t=kTFVEX0yKfNz0Eox-1)
- [x] The Audit History view includes: page title, print / download button, audit summary section, filters, searchable history list
- [x] The audit summary section supports key summary fields, where available: Status, Final Decision Date, Decision Maker
- [x] Users can filter history records by: Status, Role, Date
- [ ] Each history row supports: timestamp, actor / role, status label, optional metadata (reason, comment, attachment, or equivalent)
- [ ] The layout is reusable for multiple item types across the system.
- [ ] The visual structure remains consistent, while the actual content and available fields may vary depending on the item type.
- [ ] Exact history content and item-specific labels are out of scope for this ticket.
**Additional context**
Use the approved design as the visual reference for the Audit History layout.
This ticket defines the shared UI pattern only, not the final history content for each module or item type.
Approved ux proposal for BA - [link ](https://bcgov.sharepoint.com/:f:/r/teams/00598-TeamZelda/Shared%20Documents/Team%20Zelda/_ZEVA/ZEVA%20Rebuild/UX%20Proposals%20to%20BA/History%20tab%20+%20ZEV%20Models?csf=1&web=1&e=fz6mU8)
Attached: approved reference design.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.