bcgov / bcgov/entity

COOP correction - Enhancement Feedback

Open
#18,276 1 comment 0 reactions 0 assignees View on GitHub
UX
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

Documenting related design feedback regarding Coop corrections:

##### Correcting names
Currently a NR is required to do name correction, is it possible for staff to correct spelling errors?

##### Correcting email and phone number
When email address or phone number is corrected, users not aware that they have to close the correction filing and then delete the draft. ( Suggestion from Lance to not include this function for correction)

**Updated**: keeping this function. Will have reminder for staff not to change email / phone number in correction in the staff guide.

##### Display of special resolution text in a correction
If a coop have multiple special resolution(SR) the ledger, when making correction on an old SR, it loads the most recent SR Text, staff expect to see the one that they started correction.

**Updated**: because current correction model only loads most current information, the workaround is to display a blank Special Resolution when staff started a correction.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points; begin by locating the cooperative-correction workflow and the staff guide referenced in the body. Confirm which of the three behaviors is still in scope and define acceptance checks for name corrections, email/phone reminders, and special-resolution display before implementation.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.