-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-09-12][Search v2.1] Workspace selected in workspace switcher resets to Expensify after switching status/tab #48240
Comments
Triggered auto assignment to @madmax330 ( |
Triggered auto assignment to @anmurali ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
We think that this bug might be related to #wave-control |
@Kicu - Could you please take a look at this blocker? |
"Workspace selected in workspace switcher resets to Expensify after switching tab (Type)" is intended But I think that the "switching status" part is a bug |
ProposalPlease re-state the problem that we are trying to solve in this issue.In Step 8 and 12, the workspace selected in the workspace switcher resets to Expensify after switching to another status or tab. What is the root cause of that problem?Currently, when we click on a button in the status bar or in the search menu, we are not updating the App/src/libs/Navigation/NavigationRoot.tsx Line 159 in b9af3d1
we are setting the What changes do you think we should make in order to solve the problem?We should update the
What alternative solutions did you explore? (Optional) |
I believe it was agreed with @luacmartins that this:
is not a bug, as our expectation is that clicking on a tab resets all filters, which should include resetting |
Yea, this is not a bug (at least not yet) since we reset all filters when moving to different state/statuses. |
The selected workspace in the workspace switcher list and the breadcrumbs don't match after the reset 20240830_010838.mp4 |
cc @Kicu ^ |
I'm working today on this specific bug that selected workspace doesn't match. While it looks like a minor thing it is tightly connected to my Will be fixed |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
Payment due today |
@Kicu, @anmurali, @luacmartins Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Bump for payment @anmurali |
@Kicu, @anmurali, @luacmartins, @rayane-djouah Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@anmurali Bump for payment |
@Kicu, @anmurali, @luacmartins, @rayane-djouah Still overdue 6 days?! Let's take care of this! |
Sent @rayane-djouah an offer here |
@anmurali I work at SWM (expert agency) so no payment is required for me :) |
@Kicu, @anmurali, @luacmartins, @rayane-djouah Huh... This is 4 days overdue. Who can take care of this? |
Just pending payment to @rayane-djouah |
@Kicu, @anmurali, @luacmartins, @rayane-djouah 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@anmurali Kind bump |
@Kicu, @anmurali, @luacmartins, @rayane-djouah 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
Done. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.26-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh270803a@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
In Step 8 and 12, the workspace selected in the workspace switcher should persist.
Actual Result:
In Step 8 and 12, the workspace selected in the workspace switcher resets to Expensify after switching to another status or tab.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6585836_1724894216386.20240829_091309.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @KicuThe text was updated successfully, but these errors were encountered: