-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Distance - Distance rate changes to personal expense distance rate after editing distance #38299
Comments
Triggered auto assignment to @zanyrenney ( |
👋 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 @puneetlath ( |
@puneetlath 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 #wave-collect - Release 1 |
Looks like this is a back-end issue. @neil-marcellini I see you recently have been working on P2P distance. Any ideas about the cause? |
If it's P2P Distance related that project is moving to #vip-vsb. 👍 |
It actually affects workspace requests :( |
Yeah, being discussed here: https://expensify.slack.com/archives/C07J32337/p1710440479773439 |
A fix has been sent to Web staging. Can you please re-test? |
Note that this bug also only occurs if your personal workspace and workspace requested from have different reporting currencies. The easiest way to reproduce is to change the currency of the workspace to something other than USD. |
Just tested and it looks like it's working properly now. 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.52-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Expected Result:
The distance rate for the new distance will follow the workspace distance rate.
Actual Result:
The distance rate for the new distance follows the personal expense distance rate after changing distance.
If the distance request is edited on Collect workspace as employee, there will be a red dot next to transaction thread in LHN.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6413249_1710405338008.20240314_163248.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: