Skip to content

[Due for payment 2026-01-14] [$250] Split - App opens Inbox after refreshing Reports page with Split RHP opened #78133

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.2.84-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74652
Email or phone of affected tester (no customers): sdjisjdoinsjojsdoi@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:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Reports > Expenses.
  5. Select the expense via checkbox.
  6. Click dropdown button > Split.
  7. Refresh the page.

Expected Result:

App will stay on Reports after refreshing Reports page with Split RHP opened.

Actual Result:

App opens Inbox after refreshing Reports page with Split RHP opened.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7033734_1766153882155.27.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022002076275338339216
  • Upwork Job ID: 2002076275338339216
  • Last Price Increase: 2025-12-19
  • Automatic offers:
    • daledah | Contributor | 109893976
Issue OwnerCurrent Issue Owner: @johncschuster

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 Dec 19, 2025
  2. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    Triggered auto assignment to @johncschuster (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 Dec 19, 2025

    @melvin-bot

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

  4. github-actions commented on Dec 19, 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.
  5. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  6. 46 remaining items

  7. changed the title [-][$250] Split - App opens Inbox after refreshing Reports page with Split RHP opened[/-] [+][Due for payment 2026-01-14] [$250] Split - App opens Inbox after refreshing Reports page with Split RHP opened[/+] on Jan 7, 2026
  8. melvin-bot commented on Jan 7, 2026

    @melvin-bot

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

  9. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.94-4 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 2026-01-14. 🎊

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

  10. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    @ikevin127 @johncschuster 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]

  11. johncschuster commented on Jan 7, 2026

    @johncschuster
    Contributor

    BugZero Checklist:

    • [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 👎

  12. johncschuster commented on Jan 14, 2026

    @johncschuster
    Contributor

    Payment Summary

    Contributor: @daledah paid $250 via Upwork ✅
    Contributor+: @ikevin127 due $250 via NewDot

    @ikevin127 can you complete the BZ Checklist above when you get a moment? Thank you!

  13. ikevin127 commented on Jan 14, 2026

    @ikevin127
    Contributor

    BugZero Checklist:

    • [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: N/A - Result of the original design

    • [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: N/A

    • [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.

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

      Link to issue: https://github.com/Expensify/Expensify/issues/588838

    Regression Test Proposal

    1. Go to workspace chat.
    2. Create an expense.
    3. Go to Reports > Expenses.
    4. Select the expense via checkbox.
    5. Click dropdown button > Split.
    6. Refresh the page.
    7. Verify that the app will stay on Reports page after refreshing Reports page while Split RHP is opened.

    Do we agree 👍 or 👎.

    Zapier Logs Run ID: 00040eee-9786-a0cd-c623-d72463ced534
  14. johncschuster commented on Jan 15, 2026

    @johncschuster
    Contributor

    Thank you! Please request payment via NewDot! (Summary, here)

  15. garrettmknight commented on Jan 21, 2026

    @garrettmknight
    Contributor

    $250 approved for @ikevin127

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions