Skip to content

[Due for payment 2025-06-17] [Due for payment 2025-06-16] [Awaiting payment] Expense - Expense report is empty after paying someone #63619

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.1.60-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+060601kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM.
  3. Click + > Pay user.
  4. Enter amount > Next.
  5. Click Pay elsewhere.
  6. Click on the expense preview.

Expected Result:

Expense report will be displayed.

Actual Result:

Expense report is empty.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6851962_1749165192332.20250606_071154.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @maddylewis

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 6, 2025
  2. melvin-bot commented on Jun 6, 2025

    @melvin-bot

    Triggered auto assignment to @maddylewis (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.

  3. melvin-bot commented on Jun 6, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jun 6, 2025

    @melvin-bot

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

  5. github-actions commented on Jun 6, 2025

    @github-actions
    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.
  6. BlameGPT commented on Jun 6, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

  7. MonilBhavsar commented on Jun 6, 2025

    @MonilBhavsar
    Contributor

    Coming from #63546

  8. 31 remaining items

  9. melvin-bot commented on Jun 10, 2025

    @melvin-bot

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

  10. maddylewis commented on Jun 17, 2025

    @maddylewis
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    Do we agree 👍 or 👎

  11. maddylewis commented on Jun 17, 2025

    @maddylewis
    Contributor

    Payment Overview + Final To-Dos

    • @Ollyws requires payment through NewDot Manual Requests
    • @JakubKorytko does not require payment (Contractor)
    • Regression Test GH

    What is the amount owed for this issue?

  12. melvin-bot commented on Jun 17, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @Ollyws owed $250 via NewDot
    • Contributor: @JakubKorytko is from an agency-contributor and not due payment

    BugZero Checklist (@maddylewis)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. Ollyws commented on Jun 17, 2025

    @Ollyws
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    1. Open Expensify app.
    2. Open 1:1 DM.
    3. Click + > Pay user.
    4. Enter amount > Next.
    5. Click Pay elsewhere.
    6. Click on the expense preview.
    7. Verify that Send Money expense preview is displayed.
    

    Do we agree 👍 or 👎

  14. Ollyws commented on Jun 17, 2025

    @Ollyws
    Contributor

    @maddylewis I think it's the standard $250.

  15. melvin-bot commented on Jun 20, 2025

    @melvin-bot

    @maddylewis Whoops! This issue is 2 days overdue. Let's get this updated quick!

  16. maddylewis commented on Jun 20, 2025

    @maddylewis
    Contributor

    Payment Summary + Final To-Dos

    • Reviewer: @Ollyws owed $250 via NewDot
    • Contributor: @JakubKorytko is from an agency-contributor and not due payment
    • regression test gh
  17. Ollyws commented on Jun 20, 2025

    @Ollyws
    Contributor

    Requested in ND.

  18. garrettmknight commented on Jun 27, 2025

    @garrettmknight
    Contributor

    $250 approved for @Ollyws

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions