bcgov / bcgov/reserve-rec-admin
EPIC: Deleting a customer from the system
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 7
- Avg merge
- 12h 19m
- Merged PRs (30d)
- 37
Description
#### Description:
This ticket is to capture work related to the ability to delete a customer from the system.
This feature can be implemented closer to Frontcountry release. Considered low risk to implement sooner, unless we run into problems with people who have both BCSC and BC Parks accounts and we need to delete one.
#### Questions and considerations:
- when does this need to be implemented?
- what policies do we have in place to support this requirement?
- what is the current process and do we want to change it/make it easier for users and staff to track/be notified of requests to delete?
- what technical consideration are needed for this? (e.g., soft vs hard delete)
- PIA considerations
#### Relevant documentation:
-
#### Notes:
- Function was listed as a post release requirement for DUP
-
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by documenting the current customer-deletion process and reviewing the policy and PIA questions listed in the issue, then determine the required scope and acceptance criteria. Done means the deletion approach, timing, notifications, and technical requirements are decided and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100