Skip to content

[Due for payment 2025-12-10] [Reject] Expense - GBR remains in LHN after rejecting expense offline #70565

Closed

Description

@jponikarchuk

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.2.14-1
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 TestRail: #62787
Email or phone of affected tester (no customers): oijnoijoijjijnioj3@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. [User A] Submit an expense to User B.
  3. [User B] Open IOU expense report.
  4. [User B] Go offline.
  5. [User B] Click More > Reject.
  6. [User B] Enter reason and click Reject expense.

Expected Result:

GBR will disappear from LHN after rejecting expense offline.

Actual Result:

GBR remains in LHN after rejecting expense offline.

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

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

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

    @melvin-bot

    Triggered auto assignment to @zanyrenney (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 Sep 15, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 15, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 15, 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. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 15, 2025
  7. 53 remaining items

  8. lakchote commented on Nov 28, 2025

    @lakchote
    Contributor
  9. mananjadhav commented on Dec 2, 2025

    @mananjadhav
    Collaborator

    PR was deployed on staging.

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 3, 2025
  11. changed the title [-][Reject] Expense - GBR remains in LHN after rejecting expense offline[/-] [+][Due for payment 2025-12-10] [Reject] Expense - GBR remains in LHN after rejecting expense offline[/+] on Dec 3, 2025
  12. melvin-bot commented on Dec 3, 2025

    @melvin-bot

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

  13. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.70-0 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-12-10. 🎊

    For reference, here are some details about the assignees on this issue:

    • @mananjadhav requires payment through NewDot Manual Requests
    • @truph01 requires payment (Needs manual offer from BZ)
  14. melvin-bot commented on Dec 3, 2025

    @melvin-bot

    @mananjadhav / @truph01 @garrettmknight 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]

  15. mananjadhav commented on Dec 5, 2025

    @mananjadhav
    Collaborator

    This is deployed to production and will be paid as a part of the project. Best to close this one in a few days.

  16. mananjadhav commented on Dec 8, 2025

    @mananjadhav
    Collaborator

    I think it's safe to close this one out.

  17. trjExpensify commented on Dec 9, 2025

    @trjExpensify
    Contributor

    Do it!

  18. moved this from MEDIUM or LOW to Done in [#whatsnext] #migrateon Dec 9, 2025
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

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions