-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-04-10] [Better Expense Report View] Expense Reports - Submit and approve system message appear in report, but not pay message #58851
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
Comments
Triggered auto assignment to @sakluger ( |
Triggered auto assignment to @aldo-expensify ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
This view is behind a beta. NAB. cc @Kicu |
@Kicu, @sakluger, @luacmartins, @mountiny, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Handled as a follow up by @Kicu |
@mountiny @luacmartins I think I will need a bit of help with this one. As far as I understand the "payment" message is rendered using I've found this: Line 2675 in e2c3b27
Here are my questions
I wonder if this way of grabbing transactions and filtering out "non-chat" actions is a good approach 🤔 ? |
correct, these are "subtypes" of the IOU action. I think we'd want to keep all, except for
Not sure that I'd call it "non-chat, but yea, we'll have to filter out actions that shouldn't be visible (usually just the create ones) |
Agreed, the |
Alright will start with filtering out |
Ok can confirm that this issue will be fixed in: #58903 ![]() |
I think we can close this then! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.22-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-04-10. 🎊 For reference, here are some details about the assignees on this issue:
|
@DylanDylann @sakluger @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Uh oh!
There was an error while loading. Please reload this page.
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.1.16-1
Reproducible in staging?: Yes
Reproducible in production?: Unable to check, new feature
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp #58360
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search
Action Performed:
Precondition:
Expected Result:
Submit, approve and pay system message should all appear or not appear in the report view.
Actual Result:
Only the submit and approve system message appear in the report view. Pay system message does not appear in the report view.
Cancel payment, export to CSV system message also appear in the report view.
Workaround:
Unknown
Platforms:
Screenshots/Videos
1.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @saklugerThe text was updated successfully, but these errors were encountered: