Update URLs with account id
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
See also [Scott's spreadsheet](https://onedrive.live.com/view.aspx?resid=E52B0821EC98A357!24582&ithint=file%2cxlsx&authkey=!AO94JYayxvIowPc).
### Description
As a part of ticket #6151, the latest common components (v 2.4.38) can accept `accountid` as an URL parameter and set as current account in session storage. Some changes are needed in all page where a user can navigate between applications.
1. Breadcrumbs
2. Landing page links to application (may be handled by SbcHeader)
3. Dashboard
4. Navigation between apps, e.g; navigating to create or edit business from filings ui
**Apps to update:**
- [ ] Auth Web - #6151
- [ ] Filings UI - #10999
- [ ] Create UI - #10999
- [ ] Edit UI - #10999
- [x] Namerequest UI - #10999
- [ ] PPR UI - #11068
- [x] BC Registry UI - #10866
- [ ] FAS UI?
- [ ] Wills UI?
### Expected Behavoir - Acceptance Criteria
* GIVEN I am a user with multiple accounts
* WHEN I select another account
* THEN the current app, and apps that open via links, use the new account.
For example:
- [ ] if in Auth Web, you stay in Auth Web
- [ ] if on a BC Registries "marketing" page, redirect to the same "marketing" page for the selected account
- [ ] if in a BC Registries application, redirect to dashboard for login type and account
- what about staff - multiple accounts?
- [ ] if on Name Request, redirect to Name Request for the selected account
**Contact person:** Faiz or Severin
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with ticket #6151 and the common components version 2.4.38, then review account-selection handling across breadcrumbs, landing-page links, dashboards, and navigation between applications. Check the listed Auth Web, Filings, Create, Edit, PPR, FAS, and Wills UI work, along with related issues #10999 and #11068. Done means selecting another account preserves the account across the current app and linked applications as described by the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100