Bug Description
When editing a user in the admin panel and changing their role (e.g., from agent to administrator), the frontend does NOT include the role field in the PATCH request body.
Steps to Reproduce
- Log in as
account_owner
- Go to Users settings
- Click to edit any user
- Change the role dropdown (e.g., from Agent to Administrator)
- Click Save
Expected Behavior
The PATCH request to /api/v1/users/:id should include "role": "administrator" in the request body.
Actual Behavior
The PATCH request only sends name and availability:
PATCH /api/v1/users/:id Parameters: {"name" => "...", "availability" => "online"}
The role field is completely absent from the payload.
Backend Verification
The backend controller (Api::V1::UsersController#update) correctly handles role updates when the role parameter is present — the issue is exclusively on the frontend not including it in the request.
Environment
- Image:
evoapicloud/evo-ai-frontend-community:latest
- Deployment: Docker Swarm
- Auth service:
evoapicloud/evo-auth-service-community:latest
Bug Description
When editing a user in the admin panel and changing their role (e.g., from
agenttoadministrator), the frontend does NOT include therolefield in the PATCH request body.Steps to Reproduce
account_ownerExpected Behavior
The PATCH request to
/api/v1/users/:idshould include"role": "administrator"in the request body.Actual Behavior
The PATCH request only sends
nameandavailability:PATCH /api/v1/users/:id Parameters: {"name" => "...", "availability" => "online"}
The
rolefield is completely absent from the payload.Backend Verification
The backend controller (
Api::V1::UsersController#update) correctly handles role updates when theroleparameter is present — the issue is exclusively on the frontend not including it in the request.Environment
evoapicloud/evo-ai-frontend-community:latestevoapicloud/evo-auth-service-community:latest