Changes to Namerequest UI (Way of Navigating)
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**AS** an user
**WHEN** I need to perform an action on the Namerequest application
**THEN** the system assists me in following the optimal flow
**AND** I am directed to the appropriate flow and system
- [ ] All the businesses that already exist in BC (businesses that are already incorporated or registered in BC) will use the business lookup.
- [ ] All others will choose the business type.
- [ ] If the type is one of BC, ULC, BEN, CC they will get the option for named or numbered, and if numbered they all get text and a link of some sort. The text and link will change somewhat, but the structure should be the same.
- [ ] Firms SP/GP, and Coops, only have the named option.
- [ ] This is for all flows.
- [ ] This is the main change to the existing flow.
Design ticket:
https://app.zenhub.com/workspaces/entities-team-space-6143567664fb320019b81f39/issues/gh/bcgov/entity/12810
All the flows on 1 page:
https://www.figma.com/file/24VlKhvIajcYYqmm6VKQxx/Names-flows?type=whiteboard&node-id=52-640
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing Namerequest UI flows and compare them with the linked design ticket and Figma flow map. Trace how businesses are currently routed, then identify the changes needed across all flows. Done means existing BC businesses use lookup, other users choose a type, and each type receives the correct named or numbered path and wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100