Skip to content

[$325] [Due for payment 2025-07-15] Update Workspaces tab URLs to just workspaces to clearly differentiate them from Account-related URLs and prevent HelpPanel mismatches #64968

Closed

Description

@mountiny

Background

Previously, workspace-related pages were grouped under Account settings and shared the /settings URL prefix. That structure has changed recently. Workspaces now has its own dedicated tab, separate from Settings. However, the URLs were not updated to reflect this change in navigation. There is no redirect system in NewDot to handle old links paths (these old URLs might be referenced in bookmarks, messages or other integrations)

Problem

Both Account and Workspaces use the /settings URL prefix, even though they represent separate areas of the product
HelpPanel shows incorrect content on Workspaces pages (screenshot in 🧵)
The lack of a redirect mechanism means we can't change URLs without breaking backwards compatibility

Solution

Update all Workspaces tab URLs to start with /workspaces instead of /settings/workspaces, clearly separating them from Account-related pages and improving semantic clarity.
This change ensures:

  • A clean visual and technical distinction between Settings and Workspace sections.
  • Correct HelpPanel content rendering based on distinct URL paths.
  • Reduced confusion when users navigate or share links.
    To preserve existing user behavior and external links, implement redirects from all legacy /settings/workspaces/... URLs to their corresponding new /workspaces/... versions. This provides backward compatibility, ensures a seamless transition, and establishes a future-proof pattern for evolving routes without breaking existing references.
Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021943321028927089891
  • Upwork Job ID: 1943321028927089891
  • Last Price Increase: 2025-07-11

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 25, 2025
  2. moved this to Second Cohort - HIGH in [#whatsnext] #migrateon Jun 25, 2025
  3. melvin-bot commented on Jun 25, 2025

    @melvin-bot

    Triggered auto assignment to @johncschuster (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.

  4. sumo-slonik commented on Jun 26, 2025

    @sumo-slonik
    Contributor

    Hello, I'm Kuba from SWM and I'm getting started on this.

  5. 9 remaining items

  6. changed the title [-][Due for payment 2025-07-15] Update Workspaces tab URLs to just workspaces to clearly differentiate them from Account-related URLs and prevent HelpPanel mismatches[/-] [+][$250] [Due for payment 2025-07-15] Update Workspaces tab URLs to just workspaces to clearly differentiate them from Account-related URLs and prevent HelpPanel mismatches[/+] on Jul 10, 2025
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 10, 2025
  8. melvin-bot commented on Jul 10, 2025

    @melvin-bot

    Current assignee @allgandalf is eligible for the External assigner, not assigning anyone new.

  9. johncschuster commented on Jul 10, 2025

    @johncschuster
    Contributor

    Applying the External label to have the Upwork job created. @allgandalf, can you apply to the job linked in the OP please?

  10. allgandalf commented on Jul 11, 2025

    @allgandalf
    Contributor

    @johncschuster I applied for the job!

    @johncschuster @mountiny , The scope of work here was more than regular PR's, I tested a lot of cases for this since we updated the root url for workspaces, also went ahead and founds bugs in the help content as well which would had been overlooked otherwise.

    Considering the amount of work here, Can the price here be increased to $325 please?

  11. mountiny commented on Jul 11, 2025

    @mountiny
    ContributorAuthor

    $325 sounds good to me!

  12. changed the title [-][$250] [Due for payment 2025-07-15] Update Workspaces tab URLs to just workspaces to clearly differentiate them from Account-related URLs and prevent HelpPanel mismatches[/-] [+][$325] [Due for payment 2025-07-15] Update Workspaces tab URLs to just workspaces to clearly differentiate them from Account-related URLs and prevent HelpPanel mismatches[/+] on Jul 11, 2025
  13. melvin-bot commented on Jul 11, 2025

    @melvin-bot

    Upwork job price has been updated to $325

  14. allgandalf commented on Jul 13, 2025

    @allgandalf
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other: N/A

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other: Slack

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other: @mountiny
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: N/A we updated the routes from /settings/workspaces to /workspaces

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    This shouldn't warrant for a regression test, we simply updated the URL for workspaces tab

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    Do we agree 👍 or 👎

  15. johncschuster commented on Jul 14, 2025

    @johncschuster
    Contributor

    Payment Summary (to be issued after regression window has passed)

    Contributor: @sumo-slonik does not require payment (Contractor)
    Contributor+: @allgandalf paid $325 via Upwork ✅

  16. johncschuster commented on Jul 15, 2025

    @johncschuster
    Contributor

    Thanks for your contributions, @sumo-slonik and @allgandalf!

  17. moved this from Second Cohort - HIGH to Done in [#whatsnext] #migrateon Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions