Open motaylorvoz opened 5 years ago
Steps to repro:
So this is by design but I'm not closing it because the error message doesn't give the user any idea what is happening. A worker with assignments or signins cannot be deleted.We can't cascade because of reporting purposes. If the worker was actually signed in or assigned, they should not be deleted. They can be expired, sanctioned, or expelled.
This has not been fixed and actually it's gotten worse. Now it doesn't even say that there was an error trying to delete the worker.
What we really need to implement is "soft delete."
I propose we close this issue. This may be a permissions issue.
When I attempt to recreate with a manager role, when I push delete and accept, it does nothing (record is not deleted), and system does not let me know that I don't have enough permissions.
When I attempt to recreate with a manager role, delete works.
yes the "doesn't let me know" is the reason I kept it open, see comment above.
Unassigning myself as I am not actively working on this. Additionally if it's not blocking centers then it's really a v2 consideration, not a v1 one.
This is what was reported by Graton. They are unable to delete a worker from a data basis and it results in Error!