Bug description
Running Superset 6.0.0rc1
When editing a role, the details of users associated with that role are blank (names and email).
Those details are populated in "List Users", but do not come through when editing the roles.
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.11
Node version
I don't know
Browser
Firefox
Additional context
In the debug logs, the API call to get the users is visible and returns 200, so appears to work fine, but no user details are shown on the page: "GET /api/v1/security/users/?q=(filters:!((col:id,opr:in,value:!(4,321,1754,311,16,2,30,273,323,33,2579,18))),page:0,page_size:100) HTTP/1.1" 200
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
This looks like a frontend bug in Superset 6.0.0rc1: when editing a role, the modal fetches user details from the API but only maps the id and username fields, leaving out first_name, last_name, and email. As a result, those columns appear blank in the UI, even though the API returns the full user data and the "List Users" page displays it correctly. You can see this mapping in the RoleListEditModal component's mapResult function, which should be updated to include all relevant fields for proper display in the table view. Reference
No existing documentation or merged pull requests address this issue yet, so updating the frontend mapping logic is likely needed to resolve it.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: msyavuz
Thanks for reporting this!
Comment From: rusackas
PR linked above, if you want to test. Thanks, @msyavuz !