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
[Due for payment 2025-08-01] [$250] Expense - Chat does not scroll down after creating expense #65124
Version Number: 9.1.72-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:https://expensify.testrail.io/index.php?/tests/view/6375437 Email or phone of affected tester (no customers):sdhiuhsisudhsdisi@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Open 1:1 DM.
Send enough messages so the report is scrollable.
Open another chat.
Go back to the previous chat with many messages.
Click + > Create expense > Manual.
Submit an expense to the user.
Expected Result:
Report will scroll down to reveal the expense preview after submitting an expense to the user.
Actual Result:
Report does not scroll down to reveal the expense preview after submitting an expense to the user.
👋 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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.85-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@akinwale@joekaufmanexpensify 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]
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:
[@akinwale] 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
[@akinwale] 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
[@akinwale] 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:
Regression Test Proposal
Test:
Launch Expensify.
Open a 1:1 DM.
Send a number of messages, enough to make the report scrollable.
Open a different chat or report.
Navigate back to the previous 1:1 DM chat.
Click + > Create expense > Manual.
Submit the expense to the user.
Verify that the report scrolls to the end of the chat after the expense preview has been displayed.
Activity
melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @joekaufmanexpensify (
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.github-actions commentedon Jun 28, 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:
melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @deetergp (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 28, 2025
💬 A slack conversation has been started in #expensify-open-source
BlameGPT commentedon Jun 28, 2025
Possible culprit PRs for this issue
Exploratory PRs
61 remaining items
melvin-bot commentedon Jul 25, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.85-5 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-08-01. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 25, 2025
@akinwale @joekaufmanexpensify 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]
joekaufmanexpensify commentedon Jul 28, 2025
@akinwale could you handle checklist here so we can prep for payment later this week?
akinwale commentedon Jul 29, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[@akinwale] 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
[@akinwale] 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
[@akinwale] 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:
Regression Test Proposal
Test:
Do we agree 👍 or 👎?
joekaufmanexpensify commentedon Jul 31, 2025
Regression test issue is here.
joekaufmanexpensify commentedon Jul 31, 2025
All set to pay tomorrow!
joekaufmanexpensify commentedon Jul 31, 2025
Payment summary:
joekaufmanexpensify commentedon Aug 1, 2025
@thelullabyy $250 sent and contract ended!
joekaufmanexpensify commentedon Aug 1, 2025
Upwork job closed
joekaufmanexpensify commentedon Aug 1, 2025
@akinwale please request payment at your earliest convenience. Closing as this is otherwise all set 👍
isabelastisser commentedon Aug 5, 2025
@akinwale has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Vendor found in VML: True. Status: Active
Amount requested: $250. Matches the payment summary here.
I am not already the BZ assignee. I have approved this payment.