TFRS - Admin users can delete new user accounts before mapping
- Dominant language
- Python
- Stars
- 25
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
**Description:**
IDIR Admin and BCeID Managing Users can delete user accounts before successful mapping
Description:
As an IDIR user with the Administrator role or a BCeID user with the Managing Users I want to be able to delete user accounts that have not successfully mapped so that I can resolve duplicate accounts made in error.
Purpose:
Currently only a developer can remove duplicate accounts. Unfortunately, this issue occurs too frequently, and the Low Carbon Fuels Branch / fuel suppliers needs to be able to manage it without having to go to a developer.
**Wireframe:**
**Purpose and benefit to user:**
Low Carbon Fuels Branch / fuel suppliers needs to be able to manage it without having to go to a developer.
**Acceptance Criteria:**
- [ ] Given I am a IDIR Admin, When I am managing supplier BCeID users, then then I want to be able to delete the user prior to the account being mapped
- [ ] Given I am a BCeID Managing Users, When I am adding new BCeID users and make a mistake, then I want to be able to delete the user prior to the account being mapped
**Development Checklist:**
- [ ] A. Develop a function to determine if a user account has been successfully mapped.
- [ ] B. Create a user interface (UI) for IDIR Admin and BCeID Managing Users to delete user accounts that have not been successfully mapped.
- [ ] C. Implement a check in the delete function to ensure that only IDIR Admin and BCeID Managing Users can delete accounts that have not been mapped.
- [ ] D. Implement a check in the delete function to prevent deletion of mapped user accounts.
**Notes:**
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the supplier BCeID user-management UI and account-delete function, then verify the acceptance criteria and checklist permission and mapping checks; done means eligible unmapped accounts can be deleted by the specified roles while mapped accounts cannot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100