Complete Profile for Additional Users on BCeID Team refers to affidavit
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Describe the bug in current situation**
When a user is added to a team that authenticates with BCeID & 2FA they do not require an affidavit. This requirement is only for the administrator. When the user receives the email to join the team and follows the steps, on the Complete Profile screen under First Name and Last Name the wording "Your first name as it appears on your affidavit" and "Your last name as it appears on your affidavit" displays. This text is not applicable.
**Link bug to the User Story**
**Impact of this bug**
Low impact. May cause confusion but if a user puts in their first and last name they can proceed.
**Chance of Occurring (high/medium/low/very low)**
Low. Most teams authenticate with BCSC.
**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**
**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to 'test.bcregistry.ca/business/auth and log on to an account created using BCeID, 2 FA and Affidavit'
2. Go to 'Team Members tab'
3. Invite a team member (using an email address that is valid)
4. Have that user log on, create a BCeID, link to a 2 FA and then agree to terms
5. Review wording on Complete Profile screen
**Actual/ observed behavior/ results**
**Expected behavior**
Remove additional wording below first name and last name box for coordinators / users setting up a profile for a BCeID & 2 FA account.
**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the invited BCeID and 2FA team-member flow at the Complete Profile screen and locate the first-name and last-name helper text in the frontend. Done means the affidavit wording is absent for invited coordinators or users while the profile can still be completed; no specific file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100