You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$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
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
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
@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?
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
[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.
Activity
melvin-bot commentedon Jun 25, 2025
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.sumo-slonik commentedon Jun 26, 2025
Hello, I'm Kuba from SWM and I'm getting started on this.
9 remaining items
[-][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[/+]melvin-bot commentedon Jul 10, 2025
Current assignee @allgandalf is eligible for the External assigner, not assigning anyone new.
johncschuster commentedon Jul 10, 2025
Applying the
Externallabel to have the Upwork job created. @allgandalf, can you apply to the job linked in the OP please?allgandalf commentedon Jul 11, 2025
@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?
mountiny commentedon Jul 11, 2025
$325 sounds good to me!
[-][$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[/+]melvin-bot commentedon Jul 11, 2025
Upwork job price has been updated to $325
allgandalf commentedon Jul 13, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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/workspacesto/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 👎
johncschuster commentedon Jul 14, 2025
Payment Summary (to be issued after regression window has passed)
Contributor: @sumo-slonik does not require payment (Contractor)
Contributor+: @allgandalf paid $325 via Upwork ✅
johncschuster commentedon Jul 15, 2025
Thanks for your contributions, @sumo-slonik and @allgandalf!