-
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] Paying an iouReport elsewhere on NewDot includes a bunch of junk in the email about consumer payments #49809
Comments
Triggered auto assignment to @kevinksullivan ( |
Job added to Upwork: https://www.upwork.com/jobs/~021839397950883214755 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Triggered auto assignment to @johncschuster ( |
@johncschuster, @sobitneupane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Waiting on proposals |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I'm looking for the project this fits into and will drum up some proposals based on priority |
@johncschuster, @sobitneupane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Waiting on proposals |
Hey! I'm Eto Olei from Callstack. I will like to take a look at this issue. Please assign it to me. Thanks! |
Previously, I would have put this one into vip-vsb, but it seems like those issues are mostly being moved into newdot-quality, so I'm putting this in that project. |
Ok, BTW already started looking into this - I'm still trying to get familiar with the email notification flow basically, at least understand were such notifications are triggered, and then dig in properly why we have junks included in the email. |
Can we take a look at this from BE side, these messages seem to be sent from there. |
@johncschuster @teneeto @sobitneupane 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! |
Thanks @teneeto. Looks like a BE issue to me as well. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @luacmartins, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Looks like this is a BE issue. @luacmartins, do you have space for this one? |
My plate is quite full, so if we could get someone else to work on it that'd be great. Otherwise, I'll take a look at it some time next week. |
@blimpich, perhaps you could help here? It seems like we added all the consumer payments disclaimer stuff to an iouReport that's not actually paid in the product. |
I can look into it tomorrow 👍 |
PR up, in review |
Looks like this issue was handled completely by internal engineers. Does this require a payment summary? |
Nope, no payment summary needed 👍 |
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.40.2
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: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1727345244884739
Action Performed:
Expected Result:
The email sent on payment of the expense report doesn't include all the disclaimers for consumer payments because this iouReport was not paid with Expensify via the wallet.
Actual Result:
The email received includes all the junk about consumer payments in the footer.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: