[BT-129] Migrate Reports - Core (Part 1)

[mjasikowski]

Description

Current State:

• 5 core report routes use backTo parameter
• These handle report viewing, details, and workspace changes

Implementation:

• Replace getRoute(..., backTo) with createDynamicRoute()
• Add source screens to entryScreens array
• Remove backTo parameter from route definitions
• Test forward/back navigation

Scope

Routes (5):

Route Constant	Path
REPORT_WITH_ID	r/:reportID
REPORT_WITH_ID_DETAILS	r/:reportID/details
REPORT_WITH_ID_DETAILS_SHARE_CODE	r/:reportID/details/shareCode
REPORT_WITH_ID_DETAILS_EXPORT	r/:reportID/details/export/:connectionName
REPORT_WITH_ID_CHANGE_WORKSPACE	r/:reportID/change-workspace

Usages

REPORT_WITH_ID:

• src/pages/workspace/accounting/PolicyAccountingPage.tsx:636
• src/pages/home/report/ReportActionsList.tsx:535,626
• src/pages/home/report/PureReportActionItem.tsx:1135,1141
• src/pages/home/report/ContextMenu/ContextMenuActions.tsx:477
• src/pages/home/ReportScreen.tsx:637,762
• src/pages/Share/ShareDetailsPage.tsx:129,153

REPORT_WITH_ID_DETAILS:

• src/pages/home/report/ReportDetailsExportPage.tsx:108,133
• src/pages/RoomMembersPage.tsx:248,414,429

REPORT_WITH_ID_DETAILS_SHARE_CODE:

• Search for usages in report details flow

REPORT_WITH_ID_DETAILS_EXPORT:

• Search for usages in report export flow

REPORT_WITH_ID_CHANGE_WORKSPACE:

• Search for usages in workspace change flow

Files to modify:

• src/ROUTES.ts - Update route definitions
• src/libs/Navigation/types.ts - Remove backTo from params
• Components listed above

Migration Progress

• REPORT_WITH_ID
• REPORT_WITH_ID_DETAILS
• REPORT_WITH_ID_DETAILS_SHARE_CODE
• REPORT_WITH_ID_DETAILS_EXPORT
• REPORT_WITH_ID_CHANGE_WORKSPACE

Issue Owner

Current Issue Owner: @huult

[huult]

I’ll implement this task. cc @collectioneur.

[huult]

Screen.Recording.2026-03-02.at.13.05.54.mov

The REPORT_WITH_ID_CHANGE_WORKSPACE case is the same as described in this issue comment: #83363 (comment). The navigation changes from /e/6348904464945326?backTo=%2Fr%2F8070284288317484 to /r/6348904464945326/change-workspace?backTo=%2Fe%2F6348904464945326%3FbackTo%3D%252Fr%252F8070284288317484. We can't create dynamic route here.

@collectioneur Can we use the same approach as in this PR? #83701

[collectioneur]

@huult Makes sense. I agree that a hybrid approach would work well here, the previous case is similar. Given the complexity of these root-level routes, it might be most efficient to hold off on them for now and focus our initial efforts on migrating the simpler ones. I'm currently building out the additional logic for the dynamic routes, this will help us broaden our scope and ensure a larger number of routes can be migrated smoothly 👍