-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Split - User can split bill with only one user and billable option is present in split menu #37488
Comments
Triggered auto assignment to @puneetlath ( |
👋 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:
|
Current assignee @puneetlath is eligible for the Engineering assigner, not assigning anyone new. |
@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 #vip-split-p2p-chat-groups |
FYI, this is likely fixed by this revert. Will have QA re-test once it is CP'd. |
Splitting with one user is not a regression. |
Was fixed by revert. |
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: v1.4.45-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:
In Step 6, user should not be able to split bill with only one user. There is no split bill option from + menu in 1:1 DM.
In Stepp 7, there should be no billable option since it is not present when splitting bill.
Actual Result:
In Step 6, user is able to split bill with only one user.
In Step 7, the split preview shows billable option.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6396698_1709193921803.bandicam_2024-02-29_08-41-11-218.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: