-
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
Distance - Cannot create distance expense with duplicate start/finish + duplicate stop #34209
Comments
Triggered auto assignment to @mallenexpensify ( |
👋 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 @thienlnam ( |
I am not sure this is a bug - there are two duplicate stops that are right next to each other |
Verified this works as intended on staging |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.23-2
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
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:
Expected Result:
User should be able to create a distance expense with a duplicate start/finish with a duplicate stop.
Actual Result:
Unable to create a distance expense with a duplicate start/finish + duplicate stop.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6337314_1704854363509.Distance_exp_-_ND_-staging.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: