Skip to content

[BT-103] Migrate Workspace - Upgrade + Categories #83831

Closed

Description

@mjasikowski

Description

Current State:

  • 5 routes for workspace upgrade/downgrade and categories
  • These routes use backTo parameter for return navigation

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
WORKSPACE_UPGRADE workspaces/:policyID/upgrade/:featureName?
WORKSPACE_DOWNGRADE workspaces/:policyID/downgrade
WORKSPACE_CATEGORIES workspaces/:policyID/categories
WORKSPACE_CATEGORIES_SETTINGS workspaces/:policyID/categories/settings
WORKSPACE_CATEGORY_CREATE workspaces/:policyID/categories/new

Usages

WORKSPACE_UPGRADE:

  • src/pages/workspace/upgrade/UpgradeIntro.tsx
  • src/pages/workspace/upgrade/UpgradeConfirmation.tsx:31

WORKSPACE_DOWNGRADE:

  • src/pages/workspace/downgrade/DowngradeIntro.tsx

WORKSPACE_CATEGORIES:

  • src/pages/workspace/rules/IndividualExpenseRulesSection.tsx:51
  • src/libs/ReportUtils.ts:11548
  • src/pages/workspace/categories/ImportedCategoriesPage.tsx:134

WORKSPACE_CATEGORIES_SETTINGS:

  • src/pages/workspace/categories/WorkspaceCategoriesPage.tsx:319

WORKSPACE_CATEGORY_CREATE:

  • Search for usages in category creation flow

Files to modify:

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

Migration Progress

  • WORKSPACE_UPGRADE
  • WORKSPACE_DOWNGRADE
  • WORKSPACE_CATEGORIES
  • WORKSPACE_CATEGORIES_SETTINGS
  • WORKSPACE_CATEGORY_CREATE
Issue OwnerCurrent Issue Owner: @suneox

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Mar 2, 2026
  2. melvin-bot commented on Apr 20, 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!

  3. 38 remaining items

  4. melvin-bot commented on Aug 4, 2026

    @melvin-bot

    @suneox / @huult

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.49-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-08-11. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  5. melvin-bot commented on Aug 7, 2026

    @melvin-bot

    @suneox Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  6. melvin-bot commented on Aug 11, 2026

    @melvin-bot

    @suneox Still overdue 6 days?! Let's take care of this!

  7. huult commented on Aug 12, 2026

    @huult
    Contributor

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

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

Metadata

Metadata

Labels

DailyKSv2InternalRequires API changes or must be handled by Expensify staffSkip 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