-
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
[$250] Pay with business BA - System message is "paid x", while thread header is "paid x elsewhere" #48560
Comments
Triggered auto assignment to @isabelastisser ( |
Triggered auto assignment to @AndrewGable ( |
👋 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:
|
Trying to figure out which PR introduced this since it doesn't happen on prod |
After discussion in Slack we think this is probably a regression from the linked PR, we are going to work with @bondydaa @brandonhenry @allroundexperts to fix this regression! |
Job added to Upwork: https://www.upwork.com/jobs/~021831454888955451181 |
Current assignee @allroundexperts is eligible for the External assigner, not assigning anyone new. |
also throwing the external label on here, ideally @brandonhenry can fix but if not no need to block for that either. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Thread title and orignal message are incosistent for payment action message What is the root cause of that problem?Both strings come from different functions that are incosistent. The thread title comes from message field in reportAction which is added as part of optimistic data for payMoneyRequest. The optimistic data gets this message from getIOUReportActionMessage. The getIOUReportActionMessage function returns The message content comes from getIOUReportActionDisplayMessage. The getIOUReportActionDisplayMessage returns This causes inconsistency between thread title and the message content. getIOUReportActionMessage: Lines 4467 to 4475 in 8a35256
getIOUReportActionDisplayMessage: Lines 6933 to 6944 in 8a35256
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)Option 1Update getIOUReportActionDisplayMessage to return Option 2getIOUReportActionMessage is only used for building optmistic reports and for showing last message so maybe we can replace it with getIOUReportActionDisplayMessage. |
i'll be OOO next week so if we get proposals ready please ask for another engineer to review |
@allroundexperts, can you please review the proposal above? Thanks! |
@allroundexperts, can you please provide an update? Thanks! |
Looking at this now. |
@jaydamani can you please update your proposal to match the expected behaviour we decided above? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@allroundexperts, @isabelastisser Eep! 4 days overdue now. Issues have feelings too... |
@jaydamani Have you tried toggling the following line: |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@allroundexperts @isabelastisser this issue is now 4 weeks old, please consider:
Thanks! |
@allroundexperts After further investigating, the "Pay with Business account" option was added by #48421 (originally #37174) which was reverted #48639. So, now we only have "Pay with Expensify" and "Pay Elsewhere" for expenses. In main, the business account option is only for invoices and even for that the payment type is elsewhere so this issue is technically no longer be reproduced. However, it can happen again if new payment types are added but not updated here and here. Payment methods in 9.0.29-0: App/src/components/SettlementButton.tsx Lines 170 to 196 in 6e500c2
Payment methods in main: App/src/components/SettlementButton/index.tsx Lines 75 to 91 in 66d1025
|
@allroundexperts, can you please provide an update? Thanks! |
Since this is no longer reproducible, I think we can close this issue. |
I'm not following this. Can you confirm these steps and include a video to confirm it's not reproducible:
|
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@trjExpensify 1.New.Expensify.-.Google.Chrome.2024-10-10.18-39-25.mp4Also unrelated to this issue but, while checking I noticed that an expense is greyed out even when no changes were done after going offline Here are some rough steps for it:
Can you confirm if this is something that needs to be changed? |
@allroundexperts can you follow up on the comments above? Thanks! |
@allroundexperts, please provide an update! I will DM you for visibility, thanks! |
Great, so this bug is resolved and we can close this. |
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: 9.0.29-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4921007
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
The thread header for paid system message should be the same as the system message.
Actual Result:
The system message is "paid x", while the thread header shows "paid x elsewhere".
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6592705_1725443475664.20240904_174052.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @The text was updated successfully, but these errors were encountered: