-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$500] New order of tags do not update after reopening confirmation page #37864
Comments
Triggered auto assignment to @Christinadobrzyn ( |
👋 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:
|
Triggered auto assignment to @robertjchen ( |
@robertjchen FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think that this bug might be related to #wave6-collect-submitters cc@greg-schroeder |
Yep, not a deploy blocker per se, but definitely looks like a bug to me. Though, I'm not sure if it's on the backend cc: @greg-schroeder |
Seems like we're not sending pusher updates for the reordering. Maybe something that https://github.com/Expensify/Auth/pull/9773 will solve |
That makes sense, let's revisit after that change goes out. |
Cool, put a hold for that Auth PR - https://github.com/Expensify/Auth/pull/9773 |
PR is closed https://github.com/Expensify/Auth/pull/9773 Testing the steps in the OP again, I think this might be fixed! 2024-03-13_12-12-16.mp4Gonna ask QA to test - https://expensify.slack.com/archives/C9YU7BX5M/p1710303354198479 |
@Christinadobrzyn Bug is still reproducible by the tester. bandicam.2024-03-13.20-49-38-989.mp4 |
Ah okay, I deleted the tags in my test here, not moved them so that is the difference. I can reproduce the steps in the OP. I think this might be internal, @luacmartins @robertjchen should this remain be internal? |
|
Job added to Upwork: https://www.upwork.com/jobs/~0194dd2ee1e3003f2e |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @situchan ( |
The fix was deployed last week. @m-natarajan could you please help confirm if the issue is still reproducible? 🙏 |
Asking QA to test too - I think this is resolved - https://expensify.slack.com/archives/C9YU7BX5M/p1711355439541929 |
@Christinadobrzyn issue not reproducible anymore. 20240325_222015.mp4 |
Thanks for helping test, closing this out 👍 |
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: 1.4.48-0
Reproducible in staging?: y
Reproducible in production?: New Feature
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Precondition:
Expected Result:
The new order of multilevel tags will update when reopening the confirmation page, as it works (it updates) when changing tag name.
Actual Result:
The new order of multilevel tags does not update when reopening the confirmation page. It only updates after refreshing the page.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6404768_1709772124813.bandicam_2024-03-07_08-32-26-892.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: