[HOLD for payment 2025-01-15] [$125] Add "Go to workspace" as a shortcut in all of the workspace chats, rooms and reports details page.

[trjExpensify]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.0.64-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation: #convert thread

Action Performed:

1. Create a workspace
2. Navigate to the #admins room
3. Click the header of the chat

Expected Result:

This is a new feature

1. Add a Go to workspace row in the bottom position of the details screen of all workspace chats, rooms, threads originating from a parentChat associated with a workspace, expense reports and expense transaction threads.

2. When clicked, navigate to the workspace settings page. On small screens that'll be the LHN workspace settings page, on large screens that will be the workspace profile page.

Actual Result:

Users are getting a little lost trying to find their workspace settings, and one of the places they're commonly looking is in the details screen of the chats/reports associated with the workspace. As such, we want to provide a shortcut to get to the workspace settings from there to hopefully help.

Workaround:

N/A, improvement.

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

In-line above.

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021860062325064165317
• Upwork Job ID: 1860062325064165317
• Last Price Increase: 2024-11-22
• Automatic offers:
• mkzie2 | Contributor | 105028511

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (External)

[melvin-bot]

Current assignee @trjExpensify is eligible for the NewFeature assigner, not assigning anyone new.

[mkzie2]

Edited by proposal-police: This proposal was edited at 2024-11-20 13:47:59 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Users are getting a little lost trying to find their workspace settings, and one of the places they're commonly looking is in the details screen of the chats/reports associated with the workspace. As such, we want to provide a shortcut to get to the workspace settings from there to hopefully help.

What is the root cause of that problem?

This is a new feature

What changes do you think we should make in order to solve the problem?

1. Create a new const here for Go to workspace and a translation key for Go to workspace

2. Add the Go to workspace item here if the report?.policyID isn't fake policyID with action is a function that we will navigate to the LHN workspace settings page in small screen, navigate to the workspace profile page if it's the large screen.

if (report?.policyID && report?.policyID !== CONST.POLICY.ID_FAKE) {
    items.push({
        key: CONST.REPORT_DETAILS_MENU_ITEM.GO_TO_WORKSPACE,
        translationKey: 'common.goToWorkspace',
        icon: Expensicons.Workspace,
        action: () => {
            if (isSmallScreenWidth) {
                Navigation.navigate(ROUTES.WORKSPACE_INITIAL.getRoute(report?.policyID));
                return;
            }
            Navigation.navigate(ROUTES.WORKSPACE_PROFILE.getRoute(report?.policyID));
        },
        isAnonymousAction: false,
        shouldShowRightIcon: true,
    })
}

App/src/pages/ReportDetailsPage.tsx

Line 520 in 9f83a41

}

What alternative solutions did you explore? (Optional)