Spend - Paid by does not show the payer after selecting Received payment

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.65-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98326
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

Precondition:

• Disable Approvals and Payments in Workflows settings.

1. Go to staging.new.expensify.com
2. Create an expense in workspace chat.
3. Open the report.
4. Click Submit.
5. Click More > Recevied payment > Yes, I've received payment.
6. Go to Spend > Reports.
7. Click Display > Edit columns.
8. Select Paid by and click Save.

Expected Result:

Paid by will show the payer after selecting Received payment.

Actual Result:

Paid by does not show the payer after selecting Received payment.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7247565_1788204832371.6.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7247565

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/88748b149aaec3c6a9f825320718ed7bcb26013a07c3cad31300ef8a4b658bd6

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #98326

[github-actions]

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

[melvin-bot]

@JS00001 @hoangzinh you have been assigned to this deploy blocker because you reviewed the offending PR: #98326

[melvin-bot]

@c3024 you have been assigned to this deploy blocker because you authored the offending PR: #98326

[melvin-bot]

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