You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Expense - After merging expenses, deleted expense can be opened by navigation arrow #77610
Version Number: 9.2.78-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:#75886 Email or phone of affected tester (no customers):idjsjodijsojsdon@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses.
Open the expense report.
Open any expense.
Click More > Merge.
Select the other expense from Step 3 > Continue.
Select any details > Next.
Click Merge expenses.
Click navigation arrow on the top right.
Expected Result:
Navigation arrows on the top right should disappear after merging expenses as there is only one remaining expense in the report.
Actual Result:
Navigation arrows on the top right does not disappear after merging expenses when there is only one remaining expense in the report.
As a result, the deleted (merged) expense can be opened by the arrow which leads to a infinite loading page.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Dec 13, 2025
Triggered auto assignment to @JmillsExpensify (
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.melvin-bot commentedon Dec 13, 2025
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 13, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 13, 2025
👋 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:
15 remaining items
melvin-bot commentedon Dec 15, 2025
Current assignee @carlosmiceli is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.
m-natarajan commentedon Dec 15, 2025
Not Repro, Windows 10/ Chrome, v9.2.78-1
Repro.-.issue.77610.-.Web.mp4
daledah commentedon Dec 15, 2025
@JmillsExpensify @carlosmiceli I think me and @DylanDylann would be eligible for partial payments because this issue is marked as
Externaland i got C+ reviewed #77610 (comment) according to contributor docs:quoting from #62166 (comment)
cc @DylanDylann for more insight
daledah commentedon Dec 17, 2025
@JmillsExpensify could you please check this issue whenyou get a chance?
JmillsExpensify commentedon Dec 17, 2025
Payment summary:
JmillsExpensify commentedon Dec 17, 2025
Offer sent
JmillsExpensify commentedon Jan 20, 2026
All paid out.
garrettmknight commentedon Jan 20, 2026
Payment summary here is correct.
JmillsExpensify commentedon Jan 20, 2026
$125 approved for @DylanDylann