dosubot[bot] commented on issue #37903: URL: https://github.com/apache/superset/issues/37903#issuecomment-3886195231
<!-- Answer --> The root cause is that the frontend now only renders `user.username` in the action log table, while first/last names are available in the backend but not exposed in the API response or UI. To restore human-readable names, you can update the frontend ActionLogList component to render `user.first_name` and `user.last_name` (or a concatenated label) alongside or instead of the username. The backend already sends the full user object, so this is mainly a UI change—no database migration is needed unless you want to fetch additional fields via API parameters. For reference, see the ActionLogList code and API structure [here](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/pages/ActionLog/index.tsx#L32-L156) and [here](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/log/api.py#L25-L156). If you want to make the column customizable (e.g., toggle between username and names), you’d need to add a UI option and extend the ActionLogObject type to include all relevant user fields. This is a bit more involved but feasible. Showing both username and names is usually best for clarity, especially in environments where usernames are GUIDs. Just be mindful of privacy—displaying names in logs is standard for auditing, but check your org’s policies if you have sensitive users. Let me know if you want code pointers for the frontend change or want to discuss making the column configurable! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/97af060c-d655-433b-a229-d79f62824632?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20root%20cause%20is%20that%20the%20frontend%20now%20only%20renders%20%60user.username%60%20in%20the%20action%20log%20table%2C%20while%20first/last%20names%20are%20available%20in%20the%20backend%20but%20not%20exposed%20in%20the%20API%20response%20or%20UI.%20To%20restore%20human-readable%20names%2C%20you%20can%20update%20the%20frontend%20ActionLogList%20component%20to%20render%20%60user.first_name%60%20and%20%60user.last_name%60%20%28or%20a%20concatenated%20label%29%20alongside%20or%20instead%20of%20the%20username.%20The%20backend%20already%20sends%20the%20full%20user%20object%2C%20so%20this%20is%20mainly%20a%20UI%20change%E2%80%94no%20database%20migration%20is%20needed%20unless%20you%20want%20to%20fetch%20additional%20fields%20via%20API%20parame ters.%20For%20reference%2C%20see%20the%20ActionLogList%20code%20and%20API%20structure%20%5Bhere%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/pages/ActionLog/index.tsx%23L32-L156%29%20and%20%5Bhere%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/log/api.py%23L25-L156%29.%0A%0AIf%20you%20want%20to%20make%20the%20column%20customizable%20%28e.g.%2C%20toggle%20between%20username%20and%20names%29%2C%20you%E2%80%99d%20need%20to%20add%20a%20UI%20option%20and%20extend%20the%20ActionLogObject%20type%20to%20include%20all%20relevant%20user%20fields.%20This%20is%20a%20bit%20more%20involved%20but%20feasible.%0A%0AShowing%20both%20username%20and%20names%20is%20usually%20best%20for%20clarity%2C%20especially%20in%20environments%20where%20usernames%20are%20GUIDs.%20Just%20be%20mindful%20of%20privacy%E2%80%94displaying%20names%20in%20logs%20is%20standard%20for%20auditing%2C%20but%20c heck%20your%20org%E2%80%99s%20policies%20if%20you%20have%20sensitive%20users.%0A%0ALet%20me%20know%20if%20you%20want%20code%20pointers%20for%20the%20frontend%20change%20or%20want%20to%20discuss%20making%20the%20column%20configurable%21) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37903) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
