bcgov / bcgov/entity

Suppress log in options in header during join account flow

Open
#7,779 0 comments 0 reactions 0 assignees View on GitHub
authentication Pay
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

#### Description
When a user clicks the invitation link to join a team they are presented with an option to log in. Confusion has arisen from clients who have clicked log in in the top bar (common component) rather than through the option within the screen.

So far confusion has only been raised concerning the BCeID & 2 FA flow but the same log on issues still exist in the common component for the BC Services Card Flow as well.

![image.png](https://images.zenhubusercontent.com/5ba90c7629a785544981da1c/cb1172fc-2926-4437-af7e-e602b7843420)

![image.png](https://images.zenhubusercontent.com/5ba90c7629a785544981da1c/9491e572-bef2-4ecb-8ef2-e3002d0bbaf6)

Enhancements may be required to ensure clients are clicking the appropriate option on the screen rather than the options in the top bar.

#### Tasks
- [ ] When ticket has been created, post the ticket in RocketChat '#Operations Tasks' channel
- [ ] Add **entity** or **relationships** label to zenhub ticket
- [ ] Add 'Priority1' label to zenhub ticket
- [ ] Assign zenhub ticket to milestone: current, and place in pipeline: sprint backlog
- [ ] Reply All to IT Ops email and provide zenhub ticket number opened and which team it was assigned to
- [ ] Dev/BAs to complete work & close zenhub ticket
- [ ] Author of zenhub ticket to mark ServiceNow ticket as resolved or ask IT Ops to do so

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the join-account invitation screen and the shared top-bar login component, then compare the BCeID and 2FA flow with the BC Services Card flow. The issue names no files or tests, so first identify where these login options are rendered. Done means clients are guided to the appropriate in-screen option rather than the top-bar login during both flows.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.