bcgov / bcgov/entity

Continuation authorization for Alberta ULC could have problems

Open
#33,952 3 comments 0 reactions 0 assignees View on GitHub
bug Entities Team
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Describe the bug in current situation**
With an Alberta ULC, there is an additional document upload required (an affidavit or court order). If there is a request for change related to the affidavit / court order, the error appears in the wrong place and requires them to remove and re-upload the authorization proof in order to continue.
image.png

**Impact of this bug**
Probably minimal. Only effects Alberta ULCs, and only if there is a problem specifically with the affidavit.

**Steps to Reproduce**
1. Complete the authorization step of the Continuation In for an Alberta ULC.
2. Go to the staff review screen and marked it as "Change Requested" (I put in a comment to indicate that the affidavit had problems, but in reality there is no way to indicate which document has problems)
3. Return to client screen and notice that the error shows on the authorization proof section.

**Expected behavior**
#### FOR STAFF
**GIVEN** there is a problem with the affidavit in an Alberta ULC Continuation In
**WHEN** I send it back with changes required
**THEN** I can clearly indicate which document has the problem

#### FOR USER
**GIVEN** there is a problem with the affidavit in an Alberta ULC Continuation In
**WHEN** I view the dashboard after I see "changes requested"
**THEN** the document that has the problem is clearly indicated
**AND** I am not stopped from proceeding once I have reuploaded the correct document.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Continuation In authorization flow for an Alberta ULC, then inspect the staff review screen and client dashboard behavior after a change request. Trace how problems with the affidavit or court order are represented and displayed. Done means staff can identify the affected document and users see the correct document-specific error without being blocked after re-uploading it.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.