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
[Awaiting Checklist] [Due for payment 2025-10-01] Expense - Transaction thread has different alignment when opened in RHP and from LHN #70911
Version Number: 9.2.16-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:#70250 Email or phone of affected tester (no customers):sdoijdsoisnjdssosd33@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.
Submit two expenses to the user.
Open expense report.
Open any transaction thread.
→ The transaction thread is opened on top when it is opened in RHP.
Create a draft on the transaction thread.
Close the RHP.
Open the transaction thread from LHN.
→ The same transaction thread is not opened on top.
Expected Result:
In Step 5 and Step 8, when the transaction thread is opened in RHP and from LHN, the alignment should be the same.
Actual Result:
In Step 5, when the transaction thread is opened in RHP, the transaction thread is opened on top.
In Step 8, the same transaction thread is not opened on top when opened from LHN.
👋 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.2.17-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@c3024@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]
changed the title [-][Due for payment 2025-10-01] Expense - Transaction thread has different alignment when opened in RHP and from LHN[/-][+][Awaiting Checklist] [Due for payment 2025-10-01] Expense - Transaction thread has different alignment when opened in RHP and from LHN[/+]on Oct 2, 2025
[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: The author is aware of the change.
[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 a critical regression.
[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:
None
Test:
Open the app
Open 1:1 DM without expenses
Submit two expenses to the user.
Open expense report.
Open any transaction thread.
→ The transaction thread is opened on top when it is opened in RHP.
Create a draft comment on the transaction thread (just start typing)
Activity
melvin-bot commentedon Sep 20, 2025
Triggered auto assignment to @garrettmknight (
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 Sep 20, 2025
Triggered auto assignment to @amyevans (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 20, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 20, 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:
VickyStash commentedon Sep 22, 2025
Hey @mitarachim, I'm not sure I get the issue at 100%, could you please provide the expected result vs actual result screenshots comparison? 🙏
34 remaining items
melvin-bot commentedon Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 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-10-01. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Sep 24, 2025
@c3024 @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]
melvin-bot commentedon Sep 29, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Oct 1, 2025
Payment Summary
Upwork Job
BugZero Checklist (@garrettmknight)
garrettmknight commentedon Oct 2, 2025
@c3024 can you complete the checklist for this one?
[-][Due for payment 2025-10-01] Expense - Transaction thread has different alignment when opened in RHP and from LHN[/-][+][Awaiting Checklist] [Due for payment 2025-10-01] Expense - Transaction thread has different alignment when opened in RHP and from LHN[/+]c3024 commentedon Oct 2, 2025
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: The author is aware of the change.
[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 a critical regression.
[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 👎
garrettmknight commentedon Oct 2, 2025
Payment summary here is correct.
JmillsExpensify commentedon Oct 28, 2025
$250 approved for @c3024