bcgov / bcgov/entity

Multiple Browser Window Handling for Expired Link business migration / SAF

Open
#33,793 4 comments 0 reactions 0 assignees View on GitHub
Colin Egress
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

In user research, a participant had to use the expired link flow - she sent the email through the expired link modal and the expired link email opened a new browser window where the business appeared in the list, from there she used the manage business button (modal) to open the business, but then she used the first browser window to look at her business list and the page hadn't refreshed to show the business yet.

So in the original browser window it looks like the business was failed to be added.

**My Business Registry from the expired link affiliation modal ("second browser window"):**
image.png

**My Business Registry from original migration email ("first browser window") after she affiliated the business in the second browser window:**
image.png

We should look at solutions that would prevent the user thinking their business was not added properly.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the expired-link affiliation flow across the two browser windows and compare the My Business Registry views described in the issue. Trace how the original window learns about the newly affiliated business; done should prevent it from appearing to fail, either by reflecting the affiliation or clearly communicating the current state.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.