Skip to content

[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

Closed
8 tasks done
jponikarchuk opened this issue Mar 20, 2025 · 17 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Weekly KSv2

Comments

@jponikarchuk
Copy link

jponikarchuk commented Mar 20, 2025

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:

  • Log in with Expensifail account.
  1. Go to staging.new.expensify.com
  2. Create a new workspace.
  3. Go to workspace chat.
  4. Submit a manual expense to the workspace chat.
  5. Go to Reports.
  6. Go to Expense Reports.
  7. Click on the expense report from Step 4.
  8. Click Submit.
  9. Click Approve.
  10. Click Pay elsewhere.

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:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sakluger
@jponikarchuk jponikarchuk added Bug Something is broken. Auto assigns a BugZero manager. DeployBlockerCash This issue or pull request should block deployment labels Mar 20, 2025
Copy link

melvin-bot bot commented Mar 20, 2025

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

Copy link

melvin-bot bot commented Mar 20, 2025

Triggered auto assignment to @aldo-expensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

@melvin-bot melvin-bot bot added the Daily KSv2 label Mar 20, 2025
Copy link

melvin-bot bot commented Mar 20, 2025

💬 A slack conversation has been started in #expensify-open-source

@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Mar 20, 2025
Copy link
Contributor

👋 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:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@luacmartins
Copy link
Contributor

This view is behind a beta. NAB. cc @Kicu

@luacmartins luacmartins added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Mar 20, 2025
@mountiny mountiny self-assigned this Mar 21, 2025
@mountiny mountiny moved this to Second Cohort - CRITICAL in [#whatsnext] #migrate Mar 21, 2025
@mountiny mountiny changed the title Expense Reports - Submit and approve system message appear in report, but not pay message [Better Expense Report View] Expense Reports - Submit and approve system message appear in report, but not pay message Mar 21, 2025
@melvin-bot melvin-bot bot added the Overdue label Mar 24, 2025
Copy link

melvin-bot bot commented Mar 24, 2025

@Kicu, @sakluger, @luacmartins, @mountiny, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@mountiny
Copy link
Contributor

Handled as a follow up by @Kicu

@melvin-bot melvin-bot bot removed the Overdue label Mar 24, 2025
@Kicu
Copy link
Member

Kicu commented Mar 26, 2025

@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 IOU reportAction type. I had no idea that IOU can cover more than just start of transaction but it seems they do.

I've found this:

App/src/CONST.ts

Line 2675 in e2c3b27

REPORT_ACTION_TYPE: {
which are different types (subtypes?) of IOU actions.

Here are my questions

  1. Does what I wrote make sense? which specific types (subtypes) of IOU actions should we filter and which should we keep in the chat messages list?
  2. Seems that this logic needs changing: https://github.com/Expensify/App/blob/main/src/components/MoneyRequestReportView/MoneyRequestReportActionsList.tsx#L59 - its too simple

I wonder if this way of grabbing transactions and filtering out "non-chat" actions is a good approach 🤔 ?

@luacmartins
Copy link
Contributor

which are different types (subtypes?) of IOU actions.

correct, these are "subtypes" of the IOU action. I think we'd want to keep all, except for create, split and track

I wonder if this way of grabbing transactions and filtering out "non-chat" actions is a good approach 🤔 ?

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)

@mountiny
Copy link
Contributor

Agreed, the create would be the one to hide on an expense report. split is added to a group chat, I think, so there is no need to filter there. track I am not sure but also that sounds like something for selfDM

@Kicu
Copy link
Member

Kicu commented Mar 27, 2025

Alright will start with filtering out create and track. It will be easy to modify the set of unwanted actions later 👍

@Kicu
Copy link
Member

Kicu commented Mar 27, 2025

Ok can confirm that this issue will be fixed in: #58903

Image

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Mar 27, 2025
@trjExpensify
Copy link
Contributor

I think we can close this then!

@github-project-automation github-project-automation bot moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrate Apr 1, 2025
Copy link

melvin-bot bot commented Apr 1, 2025

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Apr 3, 2025
@melvin-bot melvin-bot bot changed the title [Better Expense Report View] Expense Reports - Submit and approve system message appear in report, but not pay message [Due for payment 2025-04-10] [Better Expense Report View] Expense Reports - Submit and approve system message appear in report, but not pay message Apr 3, 2025
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Apr 3, 2025
Copy link

melvin-bot bot commented Apr 3, 2025

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Apr 3, 2025

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:

  • @Kicu does not require payment (Contractor)
  • @DylanDylann requires payment (Needs manual offer from BZ)

Copy link

melvin-bot bot commented Apr 3, 2025

@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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Weekly KSv2
Projects
Development

No branches or pull requests

8 participants