Skip to content

feat(ai-conversations): move to explore#109874

Open
obostjancic wants to merge 1 commit intomasterfrom
ognjenbostjancic/tet-2050-move-conversations-from-insights-to-explore
Open

feat(ai-conversations): move to explore#109874
obostjancic wants to merge 1 commit intomasterfrom
ognjenbostjancic/tet-2050-move-conversations-from-insights-to-explore

Conversation

@obostjancic
Copy link
Member

@obostjancic obostjancic commented Mar 4, 2026

@obostjancic obostjancic requested a review from a team as a code owner March 4, 2026 16:12
@linear
Copy link

linear bot commented Mar 4, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 4, 2026
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

transactionSummaryRoute,
traceView,
],
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Page header breadcrumbs still link to old insights path

Medium Severity

The conversations route moved from /insights/ to /explore/, but ConversationsPageHeader still constructs conversationsBaseUrl using DOMAIN_VIEW_BASE_URL (= 'insights'). This means breadcrumb links and tab navigation in the header will point to /organizations/{org}/insights/conversations/ instead of /organizations/{org}/explore/conversations/. Users clicking breadcrumbs will be unnecessarily redirected through the old path.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants