Action logs no longer show user first/last name as of 6.0.0

[sfirke]

Bug description

This results from #33298

If you look the before & after screenshots at the top of that PR, you'll see we went from seeing the first/last name - "admin user" - to the username, "admin". That is a problem for me having deployed 6.0.0 because with my OAuth setup, the usernames are GUIDs. That was never an issue, but suddenly the action logs are not useful to me at a glance. They look like this:

Thoughts on the best way to address this? We could re-introduce the first/last name columns alongside username, or make the choice of columns customizable, or revert that decision to show username and again show only first/last name, or ... ? If it's a simple fix I can take it on, but first wanted opinions about what direction to take.

Screenshots/recordings

No response

Superset version

6.0.0

Python version

I don't know

Node version

I don't know

Browser

Firefox

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• 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.

[dosubot]

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 and here.

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!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[EnxDev]

Hey @sfirke, thanks for figuring it out. I think a good middle ground would be to display the username or email as the primary value, while making the GUID accessible on hover, in a detail view, or as an additional column.
This way, the logs remain readable at a glance while still providing the technical identifier when needed for integrations or debugging.

[jaymasiwal]

I can take this on.
Proposal: display full name as primary label and show username in parentheses to preserve readability and technical ID.

[sfirke]

@jaymasiwal that proposal sounds great to me. Before you start work, let's hear confirmation from @EnxDev - are you good with restoring to first name/last name, with username (what's currently shown) on mouse over?

(I complicated things a little by using an Azure GUID for my usernames, because that was the SSO config I got working and since usernames weren't really displayed in Superset there wasn't a reason to go back and change it to use their email for Superset's username field. Your example with "admin" as the username is not bad.)