Skip to content

[Due for payment 2025-07-22] Expense-Report header shows "x expense" instead of "x for description" after removing merchant #65974

Closed

Description

@vincdargento

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.80-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #64761
Email or phone of affected tester (no customers): jdfoidjnfonodf@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.expensify.com
  2. Open 1:1 DM.
  3. Submit two expenses with description and merchant to the user.
  4. Open expense report.
  5. Open any expense row.
  6. Click Merchant.
  7. Clear the merchant and save it.

Expected Result:

Report header will show "amount for description" because there is description.

Actual Result:

Report header shows "amount expense" when there is description after removing merchant.

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

bug.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @abekkala

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 11, 2025
  2. melvin-bot commented on Jul 11, 2025

    @melvin-bot

    Triggered auto assignment to @abekkala (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 Jul 11, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jul 11, 2025

    @melvin-bot

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

  5. github-actions commented on Jul 11, 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. vincdargento commented on Jul 11, 2025

    @vincdargento
    Author

    @abekkala FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. rushatgabhane commented on Jul 11, 2025

    @rushatgabhane
    Member

    hey @BlameGPT, kindly find the culprits

  8. BlameGPT commented on Jul 11, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

    If not above, check these

  9. 4 remaining items

  10. luacmartins commented on Jul 14, 2025

    @luacmartins
    Contributor

    This is fixed on staging.

  11. luacmartins commented on Jul 15, 2025

    @luacmartins
    Contributor

    We reverted the offending PR. Closing.

  12. self-assigned this
    on Jul 15, 2025
  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 15, 2025
  14. changed the title [-]Expense-Report header shows "x expense" instead of "x for description" after removing merchant[/-] [+][Due for payment 2025-07-22] Expense-Report header shows "x expense" instead of "x for description" after removing merchant[/+] on Jul 15, 2025
  15. melvin-bot commented on Jul 15, 2025

    @melvin-bot

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

  16. melvin-bot commented on Jul 15, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.80-8 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-07-22. 🎊

  17. melvin-bot commented on Jul 15, 2025

    @melvin-bot

    @rlinoz / @luacmartins @abekkala 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

Metadata

Metadata

Labels

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions