[Due for payment 2025-05-27] [Due for payment 2025-05-14] [Desktop Navigation] Add a new Workspaces tab to the navigators and update navigation bar styles

[mountiny]

Part of https://github.com/Expensify/Expensify/issues/468845

Implement this section of the Design doc (linking to the tasks section as this project is being handled by SWM).

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

Triggered auto assignment to @sonialiap (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[adamgrzybowski]

This one is for me 👋

[adamgrzybowski]

The draft is here. After merging other PRs from this project and removing beta, we will need to do some finishing touches. #60184

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

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

• [Desktop Navigation] Remove leftHandBar beta #61066

If no regressions arise, payment will be issued on 2025-05-14. 🎊

For reference, here are some details about the assignees on this issue:

• @adamgrzybowski does not require payment (Contractor)
• @dukenv0307 requires payment through NewDot Manual Requests

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@dukenv0307] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@sonialiap] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[sonialiap]

@mountiny do you think we need a regression test here?

[mountiny]

We have not deployed yet but we will handle the regression steps altogether

[melvin-bot]

Payment Summary

Upwork Job

• Contributor: @adamgrzybowski is from an agency-contributor and not due payment
• Reviewer: @dukenv0307 owed $250 via NewDot

BugZero Checklist (@sonialiap)

• I have verified the correct assignees and roles are listed above and updated the necessary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[sonialiap]

Deployed to production. @mountiny will the regression steps be handled in another issue so I can close this, or should I keep this open?

[mountiny]

These will be handled together as part of the project so I think we can close this - payment is the same

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

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

• [Desktop Navigation] Add a new Workspaces tab to the navigators and update navigation bar styles #60184

If no regressions arise, payment will be issued on 2025-05-27. 🎊

For reference, here are some details about the assignees on this issue:

• @adamgrzybowski does not require payment (Contractor)
• @dukenv0307 requires payment through NewDot Manual Requests

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@dukenv0307] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@sonialiap] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.