Repository navigation
[Due for payment 2025-05-30] [Desktop Navigation] Save the last visited path for the Accounts pages #62320
Description
Desktop navigation follow up
Similar to this issue #56806, which focused on the settings tab - after splitting the workspaces and Account settings to two tabs, we need to refactor the logic and keep the last visited path in the Workspace settings as well as Account settings navigator
Issue Owner
Current Issue Owner: @isabelastisserMetadata
Metadata
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon May 19, 2025
Triggered auto assignment to @isabelastisser (
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.[-]Save the last visited path for the Accounts pages[/-][+][Desktop Navigation] Save the last visited path for the Accounts pages[/+][-][Desktop Navigation] Save the last visited path for the Accounts pages[/-][+][Due for payment 2025-05-30] [Desktop Navigation] Save the last visited path for the Accounts pages[/+]melvin-bot commentedon May 23, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 23, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.50-0 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 2025-05-30. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 23, 2025
@dukenv0307 @isabelastisser @dukenv0307 The PR fixing this issue has been merged! 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]
dukenv0307 commentedon May 26, 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
[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. Yes
[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
Test:
Testcase 1:
Testcase 2:
Do we agree 👍 or 👎
mountiny commentedon May 26, 2025
Payments handled as part of the project so no need to pay here
@isabelastisser could you please help us with adding the new test rail cases? thanks!
isabelastisser commentedon May 28, 2025
All set!