sfirke opened a new issue, #37903:
URL: https://github.com/apache/superset/issues/37903

   ### 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:
   
   <img width="1376" height="473" alt="image" 
src="https://github.com/user-attachments/assets/ab41121e-b1a8-455d-aa99-953f10b8c237";
 />
   
   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.


-- 
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]

Reply via email to