fix(conversations): Show when a conversation happened on detail page#112910
Open
obostjancic wants to merge 7 commits intomasterfrom
Open
Conversation
Add a visible conversation timing summary to the detail page so it is easy to see when a conversation started and when the last message happened. This surfaces the existing span timestamps in the summary header instead of making people infer timing from the table or the message list. Refs TET-2210 Co-Authored-By: OpenAI Codex <noreply@openai.com>
github-actions
bot
added
the
Scope: Frontend
Contributor
Sentry Snapshot Testing
|
Match the rendered time element by its content instead of requiring a single exact text node. This keeps the conversation summary test aligned with how the timestamp is rendered in CI and fixes the failing Jest shard on the PR. Refs TET-2210 Co-Authored-By: OpenAI Codex <noreply@openai.com>
Place the conversation timing after the used tools metadata instead of under the title. This keeps the header focused on identity and trace links while still making the timing easy to scan, and it reuses the existing TimeSince tooltip for absolute timestamp formatting. Refs TET-2210 Co-Authored-By: OpenAI Codex <noreply@openai.com>
Move the last message timestamp before used tools in the conversation detail metadata row. This keeps the timing information earlier in the scan order while preserving the existing formatter and tooltip behavior. Refs TET-2210 Co-Authored-By: OpenAI Codex <noreply@openai.com>
…when-the-conversation-happened-when-youre-on
Remove the dedicated conversation summary test file from this change. Refs TET-2210 Co-Authored-By: OpenAI Codex <noreply@openai.com>
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
…when-the-conversation-happened-when-youre-on
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Show the conversation timing directly on the detail page header.
It was hard to tell when a conversation actually happened once you clicked into the detail view because the page only showed the conversation ID, traces, and aggregate metrics. This surfaces the existing timestamps in a more obvious place by showing when the conversation started and when the last message happened.
I also added a focused component test for the summary header so the timing display stays covered.
Refs TET-2210