You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$500] Workspace - Two different IOUs are created #35961
Version Number: 1.4.37.0 Reproducible in staging?: Y Reproducible in production?: Y 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:
We can additionally send waypoints as SplitBillParams so that BE can process this as a split bill for distance request. We can also send waypoints as transaction comment. The BE support is required to process this and send back distance transaction receipt just like it is done for normal distance requests like this:
The isDistanceRequest from splitBill can be passed to createSplitsAndOnyxDatahere. This can be used to add the receipt object created as follows here for distance request and, further, add this to the transactions here and here.
Finally, here, we display the receipt image (or map receipt image for distance request) in the split bill details page based on the availability of receipt image here. Since distance receipts do not have receiptFilename, we can remove the check for receiptFilename or conditionally check only when this is not a distance request.
Similar implementation needs to be done for splitBillAndOpenReporthere for global create menu.
What alternative solutions did you explore? (Optional)
Can we please confirm the expected behavior here?
Unlike the mentioned expected behavior in OP, it looks like we should not be showing the distance tab when the split bill is initiated via the menu.
The reason why I think so is that we do not have any support for generating split bills for distance requests.
Instead, we only support split bills for manual and scan request types.
@laurenreidexpensify
As I understand, we generate two previews for split bills. So, I am not sure why OP expects only one IOU here.
Maybe this came up as we show only one preview initially for scan requests until the scanning operation completes in the server following which the split bill generation is completed. But distance requests do not have an intermediate step like this.
What do you think about this?
@eVoloshchak@laurenreidexpensify this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!
Seems like this issue also falls within the larger plan of P2P-Distance requests-Frontend here
So curious to know what you think of the proposal here as this issue also needs BE support.
cc @neil-marcellini@koko57
@laurenreidexpensify thanks for assigning me, that makes it way more visible! I think that we should close this issue, given that we do not actually support splits for distance requests yet. We're building that out with the P2P distance requests project, and once that's done it will work properly.
The reason the option shows in app now is that we figured it wasn't worth the effort to hide the option given that we'll make it work soon. That's a bit controversial and I'm open to hiding split for distance until it's working.
Activity
melvin-bot commentedon Feb 6, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01e854e11c780c2016
[-]Workspace - Two different IOUs are created[/-][+][$500] Workspace - Two different IOUs are created[/+]melvin-bot commentedon Feb 6, 2024
Triggered auto assignment to @laurenreidexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Feb 6, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (
External)lanitochka17 commentedon Feb 6, 2024
We think that this bug might be related to #wave6
CC @greg-schroeder
nebiyuelias1 commentedon Feb 7, 2024
Can't repro this bug. I can see the map.
rojiphil commentedon Feb 7, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
When
Split billis used in a Workspace Chat, distance money request can be generated which creates inconsistency.What is the root cause of that problem?
We do not have support for generation of split bill request with
distancerequest typeWhat changes do you think we should make in order to solve the problem?
We can support split bill generation for distance request type by making use of the
splitBillhere.We can pass two more parameters
isDistanceRequestandwaypointsfor handling distance requests tosplitBilllike this hereWe can additionally send
waypointsasSplitBillParamsso that BE can process this as a split bill fordistancerequest. We can also sendwaypointsas transaction comment. The BE support is required to process this and send back distance transaction receipt just like it is done for normal distance requests like this:isDistanceRequestfromsplitBillcan be passed tocreateSplitsAndOnyxDatahere. This can be used to add thereceiptobject created as follows here fordistancerequest and, further, add this to the transactions here and here.receiptFilename, we can remove the check forreceiptFilenameor conditionally check only when this is not adistancerequest.Similar implementation needs to be done for
splitBillAndOpenReporthere for global create menu.What alternative solutions did you explore? (Optional)
rojiphil commentedon Feb 7, 2024
@laurenreidexpensify @greg-schroeder
Can we please confirm the expected behavior here?
Unlike the mentioned expected behavior in OP, it looks like we should not be showing the
distancetab when thesplit billis initiated via the menu.The reason why I think so is that we do not have any support for generating split bills for
distancerequests.Instead, we only support split bills for
manualandscanrequest types.16 remaining items
rojiphil commentedon Feb 23, 2024
Apologies for the delay. I will update the proposal today
rojiphil commentedon Feb 23, 2024
Proposal
Updated to support split bill generation for distance requests in workspace chats
cc @eVoloshchak
rojiphil commentedon Feb 23, 2024
@laurenreidexpensify
As I understand, we generate two previews for split bills. So, I am not sure why OP expects only one IOU here.
Maybe this came up as we show only one preview initially for scan requests until the scanning operation completes in the server following which the split bill generation is completed. But distance requests do not have an intermediate step like this.
What do you think about this?
melvin-bot commentedon Feb 27, 2024
@eVoloshchak @laurenreidexpensify this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!
melvin-bot commentedon Feb 27, 2024
@eVoloshchak, @laurenreidexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Feb 27, 2024
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
rojiphil commentedon Feb 27, 2024
Seems like this issue also falls within the larger plan of P2P-Distance requests-Frontend here
So curious to know what you think of the proposal here as this issue also needs BE support.
cc @neil-marcellini @koko57
laurenreidexpensify commentedon Feb 29, 2024
@neil-marcellini could you take a look - #35961 (comment) -thanks
laurenreidexpensify commentedon Mar 4, 2024
@neil-marcellini adding you for feedback on #35961 (comment)
neil-marcellini commentedon Mar 4, 2024
@laurenreidexpensify thanks for assigning me, that makes it way more visible! I think that we should close this issue, given that we do not actually support splits for distance requests yet. We're building that out with the P2P distance requests project, and once that's done it will work properly.
The reason the option shows in app now is that we figured it wasn't worth the effort to hide the option given that we'll make it work soon. That's a bit controversial and I'm open to hiding split for distance until it's working.