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] [Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open #66816
Version Number: 9.1.84-1 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://test-management.browserstack.com/projects/2148171/folder/12015343/test-cases/39318327 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: MacBook Air 15.5 Chrome, iPhone 15 iOS 18.5 Safari App Component: Chat Report View
Action Performed:
Sign in to ND with a gmail account
Create a workspace
Navigate to the workspace chat
Click "+" button next to the composer, select "Create expense". Create a manual expense, do not open the expense details
Click "+" button again, create one more expense (could be any)
Observe the Report preview in the workspace chat
Expected Result:
Second expense preview is shown next to the first expense in the workspace chat
Actual Result:
Preview of the second expense is not shown in the report preview in the workspace chat until the report is opened. Reproducible also in 1:1 chats
👋 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.
changed the title [-][Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open[/-][+][Due for payment 2025-08-01] [Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open[/+]on 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:
@parasharrajat@mallenexpensify 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]
[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: Not needed
[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:
Regression Test Proposal
Test:
Sign in to ND with a gmail account
Create a workspace
Navigate to the workspace chat
Click "+" button next to the composer, select "Create expense". Create a manual expense, do not open the expense details
Click "+" button again, create one more expense (could be any)
Activity
melvin-bot commentedon Jul 21, 2025
Triggered auto assignment to @mallenexpensify (
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 Jul 21, 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 Jul 21, 2025
Triggered auto assignment to @puneetlath (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 21, 2025
💬 A slack conversation has been started in #expensify-open-source
rushatgabhane commentedon Jul 21, 2025
@BlameGPT find culprit PR
BlameGPT commentedon Jul 21, 2025
Suspects on the loose 🕵
If not above, check these
rushatgabhane commentedon Jul 21, 2025
in other DB, that cause is #65721
so it's probably this
26 remaining items
[-][Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open[/-][+][Due for payment 2025-08-01] [Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open[/+]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
@parasharrajat @mallenexpensify 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]
mallenexpensify commentedon Jul 31, 2025
Payment Summary
Contributor+: @parasharrajat due $250 via NewDot on 8/1
@parasharrajat plz complete the BZ checklist.
parasharrajat commentedon Jul 31, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: wrap Onyx.set for derived values in a method #65721
[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: Not needed
[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:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
parasharrajat commentedon Aug 1, 2025
We can close this issue, I will request later.
melvin-bot commentedon Aug 1, 2025
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Aug 4, 2025
K, @parasharrajat , ping me if/when needed.
Test case created
parasharrajat commentedon Sep 3, 2025
Payment requested as per #66816 (comment)
quinthar commentedon Sep 15, 2025
Approved $250 to @parasharrajat