Skip to content

[BT-130] Migrate Reports - Core (Part 2) #83367

Closed

Description

@mjasikowski

Description

Current State:

  • 5 report participant routes use backTo parameter
  • These handle participants list, invites, and settings

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_PARTICIPANTS r/:reportID/participants
REPORT_PARTICIPANTS_INVITE r/:reportID/participants/invite
REPORT_PARTICIPANTS_DETAILS r/:reportID/participants/:accountID
REPORT_PARTICIPANTS_ROLE_SELECTION r/:reportID/participants/:accountID/role
REPORT_SETTINGS r/:reportID/settings

Usages

REPORT_PARTICIPANTS:

  • src/pages/ReportDetailsPage.tsx:400
  • src/pages/home/report/ReportActionItemSingle.tsx:134
  • src/pages/ReportParticipantDetailsPage.tsx:46
  • src/pages/InviteReportParticipantsPage.tsx:132
  • src/components/AvatarWithDisplayName.tsx:231

REPORT_PARTICIPANTS_INVITE:

  • src/pages/ReportParticipantsPage.tsx:237

REPORT_PARTICIPANTS_DETAILS:

  • src/pages/ReportParticipantsPage.tsx:378
  • src/pages/ReportParticipantRoleSelectionPage.tsx:33

REPORT_PARTICIPANTS_ROLE_SELECTION:

  • Search for usages in participant role flow

REPORT_SETTINGS:

  • src/pages/ReportDetailsPage.tsx:425
  • src/libs/ReportUtils.ts:6253
  • src/pages/settings/Report/WriteCapabilityPage.tsx:38

Files to modify:

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

Migration Progress

  • REPORT_PARTICIPANTS
  • REPORT_PARTICIPANTS_INVITE
  • REPORT_PARTICIPANTS_DETAILS
  • REPORT_PARTICIPANTS_ROLE_SELECTION
  • REPORT_SETTINGS
Issue OwnerCurrent Issue Owner: @suneox

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Feb 24, 2026
  2. changed the title [-][BT-P2-007] Reports - Core (Part 2)[/-] [+][BT-107] Migrate Reports - Core (Part 2)[/+] on Feb 24, 2026
  3. mananjadhav commented on Feb 24, 2026

    @mananjadhav
    Collaborator

    Taking this up as implementer.

  4. changed the title [-][BT-107] Migrate Reports - Core (Part 2)[/-] [+][BT-130] Migrate Reports - Core (Part 2)[/+] on Mar 2, 2026
  5. melvin-bot commented on Mar 25, 2026

    @melvin-bot

    This issue has not been updated in over 15 days. @mananjadhav, @mjasikowski, @huult eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  6. 22 remaining items

  7. changed the title [-][Due for payment 2026-06-23] [BT-130] Migrate Reports - Core (Part 2)[/-] [+][BT-130] Migrate Reports - Core (Part 2)[/+] on Jun 17, 2026
  8. added
    Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.
    on Jun 24, 2026
  9. huult commented on Jul 9, 2026

    @huult
    Contributor

    @mjasikowski #83367 (comment) we can close this ticket

  10. melvin-bot commented on Jul 9, 2026

    @melvin-bot

    This issue has not been updated in over 15 days. @mjasikowski, @suneox, @huult eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  11. huult commented on Jul 13, 2026

    @huult
    Contributor

    @mjasikowski #83367 (comment) we can close this ticket

    cc @mjasikowski 😄

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

Metadata

Metadata

Labels

InternalRequires API changes or must be handled by Expensify staffMonthlyKSv2Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions