bcgov / bcgov/zeva2

ZEVA 2 - BCEID user - Rename and Restyle ZEV unit Transactions as Credit Balance & Transactions

Open
#588 0 comments 0 reactions 0 assignees View on GitHub
Medium Task
Dominant language
TypeScript
Stars
1
Forks
6
Avg merge
14h 22m
Merged PRs (30d)
32

Description

**Describe the task**
Update the existing BCEID user tab ZEV Unit Transactions ( Credit Transactions)
The tab should be named Credit Balance and Transactions
The page should be restyled to match approved mockup.

**Purpose**
Improve clarity and organization of supplier credit info.

**Acceptance Criteria**
- [ ] The ZEV Unit Transactions tab is renamed to Credit Balance and Transactions
- [ ] The ZEV Unit Transactions tab matches the approved [Figma design.](https://www.figma.com/design/7Qgou3rxcHHk5qbmD9538x/ZEVA-2?node-id=3272-19820&t=xpdupCduTye12Tml-1)
- [ ] Current Balance is displayed as a summary table.
- [ ] The existing accordion/list of Compliance Years is replaced with a table-based view.
- [ ] All existing transaction data remains available.
- [ ] Transaction records are displayed using the application’s standard table component.
- [ ] Users can filter transactions by Compliance Year.
- [ ] Users can search transactions using the standard search field.
- [ ] Quick-filter buttons for recent Compliance Years are available as shown in the design.
- [ ] Selecting a Compliance Year updates the displayed transaction records.
- [ ] Existing business logic and transaction data remain unchanged.
- [ ] Typography, wording, spacing, tables, filters, and overall layout match the approved

Image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the existing BCEID user tab named ZEV Unit Transactions and review its current transaction data and controls. Compare the page with the approved Figma design and the acceptance criteria. Done means the renamed Credit Balance and Transactions tab provides the summary and transaction tables, compliance-year filters, search, quick filters, and unchanged transaction data.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.