Corrections UI Work
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This ticket is intended to act as a top level ticket for all required UI changes for the correction filings.
Corrections work should align with the new direction for Corrections filings:
1. Corrections should change current data
2. Correctable fields: https://bcgov-my.sharepoint.com/:x:/r/personal/thayne_werdal_gov_bc_ca/_layouts/15/doc2.aspx?sourcedoc=%7B8812EAF0-9920-404C-A709-EB17FC5A78C1%7D&file=Requirements%20-%20Filings%20vs%20Corrections%20Fields.xlsx&action=default&mobileredirect=true
3. RAID ticket available [here](https://app.zenhub.com/workspaces/raid--work-space-617c3d4cef313f001d715a7c/issues/gh/bcgov-registries/raid/791)
4. Initial designs are available here: https://www.figma.com/design/6VCttiaobFtKqZPecb9Saj/Business-Dashboard?node-id=645-13293&m=dev
Possible items to consider:
- Net New components required
- Components that require updates
- Which filing type updates should allow which components
- Integration of role specific views
- decide on submission strategy, how best to get data to API
- ?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked requirements spreadsheet and Figma designs, then review the RAID ticket for the correction-filings direction. Define the required new and updated components, filing-type permissions, role-specific views, and API submission strategy; done requires these UI areas and integration decisions to be implemented consistently with those sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100