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-23] [$250] Tooltip - Tooltip is cut off when the workspace chat is partially visible #58132
Version Number: 9.1.11-1 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):sdoijsdnoijsisd@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Left Hand Navigation (LHN)
Action Performed:
Go to staging.new.expensify.com
Create a new Gmail account.
Finish the onboarding.
Create many workspaces until LHN is scrollable.
Go to Inbox.
Open FAB to dismiss the tooltip if needed.
Scroll to the bottom to show the workspace chat with tooltip.
Scroll up slightly so that the workspace chat is not entirely visible.
Expected Result:
Tooltip will be shown completely or it should only display when the chat is completely visibly.
Actual Result:
Tooltip is cut off when the workspace chat is partially visible.
👋 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.
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:
[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.
[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: regression wasn't critical
[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. Is it easy to test for this bug? No (you need a new account to test this)
Is the bug related to an important user flow? yes
Is it an impactful bug? No (Near zero impact, I don't think we need a regression test for this)
Activity
melvin-bot commentedon Mar 11, 2025
Triggered auto assignment to @kadiealexander (
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 11, 2025
Triggered auto assignment to @robertjchen (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 11, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 11, 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:
57 remaining items
kadiealexander commentedon Apr 17, 2025
Reassigning to handle payment as I'm heading OOO. Thanks for your help @adelekennedy!
adelekennedy commentedon Apr 21, 2025
Payment due on the 23rd
adelekennedy commentedon Apr 24, 2025
Payment Summary
$250 @eVoloshchak (NewDot)
$250 @thelullabyy (Upwork)
adelekennedy commentedon Apr 24, 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:
[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 👎
melvin-bot commentedon Apr 28, 2025
@robertjchen, @eVoloshchak, @adelekennedy, @thelullabyy Whoops! This issue is 2 days overdue. Let's get this updated quick!
eVoloshchak commentedon Apr 28, 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: https://github.com/Expensify/App/pull/56209/files#r2063987890
[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: regression wasn't critical
[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.
Is it easy to test for this bug? No (you need a new account to test this)
Is the bug related to an important user flow? yes
Is it an impactful bug? No (Near zero impact, I don't think we need a regression test for this)
garrettmknight commentedon Dec 7, 2025
$250 approved for @eVoloshchak