Skip to content

[Due for payment 2025-05-14] [Due for payment 2025-05-13] [$125] LHN - Tooltip on Concierge chat, reappears after submitting first WS expense and deleting it #61351

Closed

Description

@nlemma

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.1.39-2
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - new feature
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): ibellicotest+649@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Left Hand Navigation (LHN)

Action Performed:

  1. Open the staging.new.expensify.com website.
  2. Sign up with a new account.
  3. Skip the "What´s your work Email?" modal
  4. Select "track and budget expenses" on next step and complete the oboarding modal.
  5. Note that when landing in inbox, a tooltip is displayed on "Concierge" chat.
  6. Dismiss the tooltip.
  7. Tap on FAB and select "New Workspace"
  8. Complete the creation flow.
  9. Return to inbox and open the just created workspace chat.
  10. Submit a manual expense.
  11. Long tap on the preview of the just created expense and delete it.
  12. Return to inbox.
  13. Note that tooltip on Concierge chat appears again.

Expected Result:

"You´ll see (GBR) on actions to take, and (RBR) on errors to review" tooltip on Conciege chat, shouldn´t reappear after being dismissed.

Actual Result:

"You´ll see (GBR) on actions to take, and (RBR) on errors to review" tooltip on Concierge chat, reappears after creating first workspace expense and deleting it, despite having been dismissed before.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6819919_1746213749455.Tooltip.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021918425008927190760
  • Upwork Job ID: 1918425008927190760
  • Last Price Increase: 2025-05-02
Issue OwnerCurrent Issue Owner: @kadiealexander

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on May 2, 2025
  2. melvin-bot commented on May 2, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on May 2, 2025

    @melvin-bot

    Triggered auto assignment to @blimpich (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on May 2, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on May 2, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. nlemma commented on May 2, 2025

    @nlemma
    Author

    @kadiealexander FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. blimpich commented on May 2, 2025

    @blimpich
    Contributor

    Not a deploy blocker, demoting.

  8. 12 remaining items

  9. alitoshmatov commented on May 4, 2025

    @alitoshmatov
    Contributor

    No proposals, might be fixed by above mentioned PR

  10. rayane-d commented on May 5, 2025

    @rayane-d
    Contributor

    I tested and confirmed that this issue is resolved by PR #61338

  11. blimpich commented on May 5, 2025

    @blimpich
    Contributor

    Yay! Closing

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on May 6, 2025
  13. changed the title [-][$125] LHN - Tooltip on Concierge chat, reappears after submitting first WS expense and deleting it[/-] [+][Due for payment 2025-05-13] [$125] LHN - Tooltip on Concierge chat, reappears after submitting first WS expense and deleting it[/+] on May 6, 2025
  14. melvin-bot commented on May 6, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.39-8 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-05-13. 🎊

    For reference, here are some details about the assignees on this issue:

  15. melvin-bot commented on May 6, 2025

    @melvin-bot

    @alitoshmatov @kadiealexander @alitoshmatov 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]

  16. changed the title [-][Due for payment 2025-05-13] [$125] LHN - Tooltip on Concierge chat, reappears after submitting first WS expense and deleting it[/-] [+][Due for payment 2025-05-14] [Due for payment 2025-05-13] [$125] LHN - Tooltip on Concierge chat, reappears after submitting first WS expense and deleting it[/+] on May 7, 2025
  17. melvin-bot commented on May 7, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.40-7 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-05-14. 🎊

    For reference, here are some details about the assignees on this issue:

  18. melvin-bot commented on May 7, 2025

    @melvin-bot

    @alitoshmatov @kadiealexander @alitoshmatov 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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions