The mentor create / edit form exposes a "Profile Status" dropdown with four options: Active, Disabled, Banned, Pending. The platform only recognises three statuses: ACTIVE, PENDING, REJECTED. "Disabled" and "Banned" do not exist anywhere in the system.
On create, the admin's selection is ignored regardless of what they pick. Every new mentor is saved with profileStatus: PENDING and is moved to ACTIVE or REJECTED only through the dedicated approve / reject endpoints.
Steps to reproduce
- Open "Create mentor" in the admin portal.
- Fill all required fields. In "Profile Status" pick "Active" (or "Disabled", or "Banned").
- Save and read the mentor back.
Expected
- The dropdown lists only statuses the platform supports.
- On create, the status control is not shown — new mentors always start as
PENDING and move via approve / reject.
- On edit, the dropdown is shown but limited to legitimate transitions for the current state.
Actual
- "Disabled" and "Banned" are offered but cannot be persisted.
- Whatever the admin picks, the saved mentor comes back as
profileStatus: PENDING. The selection is silently ignored — no error, no warning.
Impact
The admin makes a choice the system ignores. Two of the four offered options have no meaning in the platform at all, so the admin's mental model of mentor states is wrong from the start. There is no signal that the dropdown is fake.
How to verify it is fixed
- The create form no longer shows a "Profile Status" control. New mentors are always created in
PENDING.
- The edit form's status options match the backend enum exactly (
ACTIVE, PENDING, REJECTED — no Disabled, no Banned).
- On the edit form, picking a value and saving round-trips correctly, and the public mentor list reflects the change.
- If the team wants
Disabled / Banned as real states, they are added to the backend ProfileStatus enum, given migrations, and exposed via the proper transition endpoints — not as silent dropdown values.
The mentor create / edit form exposes a "Profile Status" dropdown with four options:
Active,Disabled,Banned,Pending. The platform only recognises three statuses:ACTIVE,PENDING,REJECTED. "Disabled" and "Banned" do not exist anywhere in the system.On create, the admin's selection is ignored regardless of what they pick. Every new mentor is saved with
profileStatus: PENDINGand is moved toACTIVEorREJECTEDonly through the dedicated approve / reject endpoints.Steps to reproduce
Expected
PENDINGand move via approve / reject.Actual
profileStatus: PENDING. The selection is silently ignored — no error, no warning.Impact
The admin makes a choice the system ignores. Two of the four offered options have no meaning in the platform at all, so the admin's mental model of mentor states is wrong from the start. There is no signal that the dropdown is fake.
How to verify it is fixed
PENDING.ACTIVE,PENDING,REJECTED— noDisabled, noBanned).Disabled/Bannedas real states, they are added to the backendProfileStatusenum, given migrations, and exposed via the proper transition endpoints — not as silent dropdown values.