Repository navigation
feat(site): use display name field for tasks - #20918
Conversation
f613ff0 to
576fe31
Compare
576fe31 to
f449045
Compare
mafredri
left a comment
There was a problem hiding this comment.
LGTM! 👍🏻
Re: @DanielleMaywood's concern, I think the name is more suitable there than the display name (especially considering space constraints), but it could be a bit confusing. I think we can wait for customer feedback on this, though.
I also had that question, but I think it makes sense to keep showing the task name because we already show the display name in the sidebar. This way, the user is able to more easily identify which task name is associated with the task display name. Additionally, since the workspace name matches the task name, showing the task name in the top bar helps users connect the task to its associated workspace when navigating between views. Started an internal thread on slack regarding this topic: https://codercom.slack.com/archives/C0992H8HGCS/p1764086497375829 |


Description
This PR updates the frontend to use the new
display_namefield for tasks. In the tasks list view,display_namereplacesinitial_prompt, and in the tasks sidebar,display_namereplacesname. This is a follow-up to #20856, which introduced thedisplay_namefield in the backend.Changes
task.display_nameinstead oftask.initial_promptin the tasks tabletask.display_nameinstead oftask.namein the task sidebar viewdisplay_namefor all test tasksFollow-up: #20856
Closes: #20801