Open IuliiaHerets opened 2 months ago
@trjExpensify Bump agian
Sorry I am not entirely clear what the question is. Can you please restate the problem?
I totally missed these pings for some reason as well, my bad. Same boat as Doza, I don't really understand what we're doing in this issue or what the problem is.
@davidcardoza @trjExpensify In individual invoice creation, we fix the invoice payer using property in the report for the whole invoice room. So, should we create a separate invoice room when the invoice payer creates an invoice for the previous invoice creator? Please check the issue steps to get more clarity.
I think I am following, referencing the OP the problem seems to be this:
User B (invoice receiver and also admin of the workspace) is able to pay the invoice that User B sends.
In short, users can currently pay their own invoices, which we should prevent. Let’s lock this down by hiding the "Pay" button in the IOU preview from the invoice sender.
In short, users can currently pay their own invoices, which we should prevent. Let’s lock this down by hiding the "Pay" button in the IOU preview from the invoice sender.
But user A can't pay this either. This is the problem we are facing.
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@shubham1206agra bump!
@OfstadC, @shubham1206agra Huh... This is 4 days overdue. Who can take care of this?
@trjExpensify @davidcardoza Bump on https://github.com/Expensify/App/issues/47174#issuecomment-2375856373
In your example you stated "[User A] Send an invoice to User B from the same workspace in Step 2." So in this case User A sent an invoice, so they shouldn't be able to pay their invoice. Perhaps you can record a new flow of this issue occurring to help us better conceptualize the workflow. That would be helpful.
@IuliiaHerets Can you ask for new recording from Applause?
In step 7: [User B] Note that User B can send and pay their own invoice. - Able to reproduce this still Error will show up if User B pays their own invoice as business for the second time. - Not reproduced now. Video:
https://github.com/user-attachments/assets/57098024-631f-4f6c-b661-958889f0ff5b
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
Any further update @shubham1206agra ? 😃
@OfstadC, @shubham1206agra Huh... This is 4 days overdue. Who can take care of this?
@OfstadC, @shubham1206agra 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
Bump @shubham1206agra
Waiting for @davidcardoza for response here
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@OfstadC, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
@madmax330 Can you chime in here https://github.com/Expensify/App/issues/47174#issuecomment-2352859330?
Is the issue that the sender of the invoice can pay the invoice? I assume we only want the receiver, or any admin in the receiving workspace to be able to pay the invoice right @davidcardoza
Bump @shubham1206agra @OfstadC
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@OfstadC, @shubham1206agra Eep! 4 days overdue now. Issues have feelings too...
As noted here, we don't want anyone to be able to pay their own invoice. (Slack convo)
Can someone clarify where the confusion is 😅 ? I'm not sure what we are waiting on here @shubham1206agra @MuaazArshad
Ok The thing I am waiting on is that the logic in BE is wrong as the invoice room is locked for single payer, which should not happen
@OfstadC, @shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@OfstadC, @shubham1206agra 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
I am not sure what should we do next here. Since this is stuck on decision.
I think I might be confused about where we are stuck here 😅
Wait let me start a thread on slack.
https://expensify.slack.com/archives/C01GTK53T8Q/p1730301321468289
@shubham1206agra From what I’m seeing, it seems that we should restrict a user from paying invoices they send within the same workspace to prevent confusion or errors. Let me know if that aligns with your understanding or if there’s anything further to clarify!
@shubham1206agra From what I’m seeing, it seems that we should restrict a user from paying invoices they send within the same workspace to prevent confusion or errors. Let me know if that aligns with your understanding or if there’s anything further to clarify!
@davidcardoza I agree with this statement. But the problem is that the payer is getting locked to a single person, and hence other admins cannot do payout here. So shouldn't we do something here?
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
@OfstadC, @shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!
Yes we should fix that and open up the ability to pay an invoice to other admins in the invoice room.
@davidcardoza Can you take this internal then?
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: v9.0.18-7 Reproducible in staging?: Y Reproducible in production?: Y Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
User B (invoice receiver and also admin of the workspace) should not be able to pay the invoice that User B sends.
Actual Result:
User B (invoice receiver and also admin of the workspace) is able to pay the invoice that User B sends. When User B pays their own invoice as business for the second time, error shows up.
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/58fd96d7-77ff-4297-9b9f-15a6758806a0
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @shubham1206agra