-
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
[$500] Inconsistent Usage of 'Paid' and 'Spent' in Request Money Details #29796
Comments
Triggered auto assignment to @maddylewis ( |
Job added to Upwork: https://www.upwork.com/jobs/~01c684e7bddef28b1a |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Inconsistent Usage of 'Paid' and 'Spent' in Request Money Details. What is the root cause of that problem?When using In Lines 1436 to 1438 in a24e6a0
We are returning the What changes do you think we should make in order to solve the problem?Return What alternative solutions did you explore? (Optional)N/A |
📣 @brunovjk! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@Charan-hs the PR you mentioned is related to the Request Money feature, so using Spent seems to be fine But, In the context of the function Send Money, the word Paid is more appropriate as it signifies a transaction between two accounts, while Spent has a broader, more general meaning. More importantly, it should be used consistently between the IOU preview and the header of the chat report. |
This is an intentional change. Any IOUs containing non-reimbursable transactions will display "A Spent X". In our use case though, Spent is actually an alternative for Owes not Paid. So Both the LHN and Report Preview should display Paid in this case. That said, it looks like there's a minor bug where the LHN is displaying the wrong message. I think the problem is somewhere in this logic, though I can't look too deep into it at this moment Line 1607 in 6d937cc
Line 1619 in 6d937cc
versus App/src/components/ReportActionItem/ReportPreview.js Lines 170 to 172 in 6d937cc
Though you can see in the linked PR where we update these headers. Perhaps we need to create a single function for the name or rename/use |
ProposalPlease re-state the problem that we are trying to solve in this issue.Inconsistent Usage of 'Paid' and 'Spent' in Request Money Details What is the root cause of that problem?here we are not properly checking for the report like weather it's settled or not then we should check for the Reimbursable. Along with this, I think there is a BE problem because Line 1436 in a24e6a0
this condition is not validated it to true so getMoneyRequestReportName returned message as Paid
What changes do you think we should make in order to solve the problem?As here #29796 (comment) mentioned right, we should do the same logic/validatation to check for all Parameters. here we should add new constion to check for the |
@tranvantoan-qn, @grgia Thanks for the valuable insights |
@Ollyws, @grgia, @maddylewis Huh... This is 4 days overdue. Who can take care of this? |
@Ollyws do any of the proposals look good to you? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Will get to this one asap. |
@Ollyws, @grgia, @maddylewis Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I can't reproduce this on the latest staging. The labels in the report action item and the header both say "paid" rather than "spent". |
@Ollyws @grgia @maddylewis this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Let's close out 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: 1.3.85-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: @tranvantoan-qn
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697547094539339
Action Performed:
Expected Result:
The labels 'Paid' or 'Spent' should remain the same both before and after viewing the details
Actual Result:
Inconsistent Usage of 'Paid' and 'Spent' in Request Money Details
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android.-.Native.mov
Android: mWeb Chrome
Android.-.Chrome.mov
iOS: Native
iOS.-.Native.MP4
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS.-.Chrome.mp4
Recording.110.mp4
MacOS.-.Safari.mov
MacOS: Desktop
MacOS.-.Desktop.mov
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: