Skip to content

[Tracking] Investigate usages of backTo and forwardsTo query params and remove them #67284

Closed

Description

@mountiny

Coming from this thread.

The backTo and forwardsTo params make the URLs look dense and ugly, in extension making UX worse. Let's try to find ways to remove them, either by creating new routes for flows which would benefit from it, dropping the user to the original flow, when it comes to things like settings.

We will make sure to:

  • Mark adding new goBack param as deprecated with a warning so people do not add more instances of these
  • Update the documentation about the backTo param to indicate how the developer should go about the situations when they think they need the param
  • Update the test case to ensure the expected navigation is captured there
Issue OwnerCurrent Issue Owner: @mountiny

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 28, 2025
  2. melvin-bot commented on Jul 28, 2025

    @melvin-bot

    Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on Jul 31, 2025

    @melvin-bot

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

  4. mountiny commented on Aug 4, 2025

    @mountiny
    ContributorAuthor

    Working through this one

  5. melvin-bot commented on Aug 6, 2025

    @melvin-bot

    @adamgrzybowski 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  6. melvin-bot commented on Aug 8, 2025

    @melvin-bot

    @adamgrzybowski 10 days overdue. Is anyone even seeing these? Hello?

  7. adamgrzybowski commented on Aug 11, 2025

    @adamgrzybowski
    Contributor

    We are investigating 👁️ 👁️

  8. 83 remaining items

  9. mountiny commented on Dec 16, 2025

    @mountiny
    ContributorAuthor

    Design doc is soon going to be in detailed review

  10. mallenexpensify commented on Dec 23, 2025

    @mallenexpensify
    Contributor

    @mountiny if a C+ is needed for reviews, please remove/add External

  11. mountiny commented on Jan 26, 2026

    @mountiny
    ContributorAuthor

    There is a design doc that is handling big chunk of this, leaving this open to see where we are at after the doc

  12. mountiny commented on Mar 10, 2026

    @mountiny
    ContributorAuthor

    The projects to update the routing are under wat

  13. mountiny commented on Apr 14, 2026

    @mountiny
    ContributorAuthor

    This is being handled in separate quality project, I think we can close this issue now

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.MonthlyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions