Engagement Dashboard close button does not navigate when opened via Workspace -> 'See on Engagement Dashboard'

Description:

When accessing the Engagement Dashboard through two different navigation paths, the close (X) button behaves inconsistently.

If the Engagement page is opened directly through Admin → Engagement, clicking the close button correctly redirects the user to the Home page.

However, when the Engagement Dashboard is opened through Workspace → “See on Engagement Dashboard”, clicking the close (X) button does not navigate away from the page. The page remains on the Engagement dashboard even though the internal navigation state appears to change in the developer tools.

https://github.com/user-attachments/assets/0f0be302-3b4f-4ad3-9125-1ccbaa4d8f32

Steps to reproduce:

1. Go to the Home page
2. Navigate to Admin → Engagement
3. Click the close (X) button

Observe that the page correctly redirects to the Home page

Second scenario (bug):

1. Go to the Home page
2. Navigate to Workspace
3. Click “See on Engagement Dashboard”
4. Click the close (X) button

Observe that the page does not navigate away from the Engagement dashboard

Note: The internal link/state visible in the developer tools changes, but the visible URL in the browser does not update and the UI does not navigate away from the page.

Expected behavior:

Clicking the close (X) button should consistently navigate the user back to the appropriate previous view (such as the Home page or Workspace) regardless of how the Engagement Dashboard was opened.

Actual behavior:

When the Engagement Dashboard is opened via Workspace → “See on Engagement Dashboard”, clicking the close button does not navigate away from the page. The visible browser URL remains unchanged and the UI stays on the Engagement dashboard.

(A short screen recording demonstrating both scenarios is attached.)

Server Setup Information:

• Version of Rocket.Chat Server: Develop branch (local development environment)
• License Type: Community
• Number of Users: N/A (local instance)
• Operating System: Linux
• Deployment Method: Local development setup
• Number of Running Instances: 1
• DB Replicaset Oplog: Not configured
• NodeJS Version: v22.18.0
• MongoDB Version: Meteor bundled MongoDB

Client Setup Information

• Desktop App or Browser Version: Chromimum(latest)
• Operating System: Linux

Additional context

A short screen recording demonstrating both navigation flows has been attached to illustrate the inconsistent behaviour.

Video description

Video demonstration of the issue:

The recording shows two navigation flows to the Engagement Dashboard.

Scenario 1 (expected behavior):
Admin → Engagement → Close (X)
The page correctly navigates back to the Home page.

Scenario 2 (bug):
Workspace → "See on Engagement Dashboard" → Close (X)
The page does not navigate away from the Engagement dashboard.

The developer tools show that the internal navigation state changes, but the visible URL and UI remain on the Engagement page.

If this behavior is not intended, I would be happy to submit a fix.

Relevant logs:

No relevant errors were observed in the browser console or server logs during reproduction of the issue.

Additional observation

While further testing, I noticed another related behaviour.

When the Engagement Dashboard is opened via:

Workspace → "See on Engagement Dashboard"

the Admin sidebar navigation becomes unresponsive:

• Sidebar links do not navigate to other admin pages
• The close (X) button logs the navigation event but the UI does not change
• Other sidebar items also appear non-functional

However, when the Engagement Dashboard is opened through:

Admin → Engagement

all sidebar navigation works correctly.

This suggests the Engagement Dashboard may not be entering the Admin routing context correctly when opened from the Workspace page.

Reproduce both entry points: Admin → Engagement and Workspace → “See on Engagement Dashboard,” then inspect the Engagement Dashboard close-button handler and routing context. Compare the navigation state and visible URL in each flow; done means the close button and Admin sidebar consistently navigate away from the dashboard in both scenarios.