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-04-03] Report- Report view shakes after returning from Reports & bottom tab moves after saving search #57807
Version Number: 9.1.9-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+ps309@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Chat Report View
Action Performed:
Bug 1:
Go to staging.new.expensify.com
Go to workspace chat.
Submit an expense.
Go to Reports.
Go to Inbox.
If the display is wide, page zoom in might be required to reproduce this issue.
Bug 2:
Go to staging.new.expensify.com
Go to Reports.
Click Filters.
Apply filter that will return results.
Click Save search.
Expected Result:
Bug 1: Report view will not shake after returning from Reports.
Bug 2: Bottom tab on LHN will not move after saving search.
Actual Result:
Bug 1: Report view shakes after returning from Reports.
Bug 2: Bottom tab on LHN moves after saving search.
👋 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 [-]Report- Report view shakes after returning from Reports & bottom tab moves after saving search[/-][+][Due for payment 2025-04-03] Report- Report view shakes after returning from Reports & bottom tab moves after saving search[/+]on Mar 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.19-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@mananjadhav@RachCHopkins@mananjadhav 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: NA
[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.
I don't think we need a regression test on this one. @mollfpr While the issue says not reproducible on Production I was able to, hence I tagged it as production in the checklist.
Activity
melvin-bot commentedon Mar 5, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 5, 2025
Triggered auto assignment to @RachCHopkins (
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 Mar 5, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 5, 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:
mollfpr commentedon Mar 5, 2025
I can't reproduce the bug 1.I can reproduce it, and I see that the RHN panel is shown for a brief moment. I believe this is related to the current implementation of HelpPanel.
35 remaining items
blazejkustra commentedon Mar 27, 2025
Thank you @mananjadhav! PR got merged and we can slowly close this issue 😄
[-]Report- Report view shakes after returning from Reports & bottom tab moves after saving search[/-][+][Due for payment 2025-04-03] Report- Report view shakes after returning from Reports & bottom tab moves after saving search[/+]melvin-bot commentedon Mar 27, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.19-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-04-03. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 27, 2025
@mananjadhav @RachCHopkins @mananjadhav 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]
mananjadhav commentedon Apr 2, 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: Initial implementation of the Side Pane #56490 (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: NA
[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.
I don't think we need a regression test on this one. @mollfpr While the issue says not reproducible on Production I was able to, hence I tagged it as production in the checklist.
@RachCHopkins This is ready for payout.
RachCHopkins commentedon Apr 2, 2025
Payment Summary:
No upwork job
RachCHopkins commentedon Apr 2, 2025
Ready to pay @mananjadhav
garrettmknight commentedon Apr 10, 2025
$250 approved for @mananjadhav