Skip to content

[Due for payment 2025-07-15] [$250] Tooltip-Tooltip on the "expense reports" filter is not displayed #61099

Closed

Description

@jponikarchuk

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.33-8
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #58721
Email or phone of affected tester (no customers): agexptest+pr2904.4@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10/ Chrome, Samsung S23FE/ Android 14
App Component: Other

Action Performed:

  1. Create an account on staging.expensify.com (OldDot), choosing the 10+ employees option on signup, so that you are directed to Expensify Classic
  2. In the browser console, run the following code snippet:
    NVP.set('tryNewDot', {
    "classicRedirect": {
    "dismissed": "false",
    "timestamp": "2024-10-28 20:04:24.610"
    },
    "nudgeMigration": {
    "timestamp": "2024-10-28 20:04:24.610"
    }
    })
  3. Sign out and back in
  4. Click on the "Try New Expensify" button in the right panel
  5. You will get redirected to NewDot and see the modal
  6. Dismiss the modal
  7. Verify that the tooltip on the "expense reports" filter is displayed

Expected Result:

Tooltip on the "expense reports" filter is displayed.

Actual Result:

Tooltip on the "expense reports" filter is not displayed.

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

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021922333040188144414
  • Upwork Job ID: 1922333040188144414
  • Last Price Increase: 2025-06-03
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @CortneyOfstad

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 29, 2025
  2. melvin-bot commented on Apr 29, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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 5, 2025

    @melvin-bot

    @CortneyOfstad Huh... This is 4 days overdue. Who can take care of this?

  4. CortneyOfstad commented on May 6, 2025

    @CortneyOfstad
    Contributor

    I am unable to consistently recreate, so going to get this retested

  5. added
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on May 6, 2025
  6. CortneyOfstad commented on May 9, 2025

    @CortneyOfstad
    Contributor

    Waiting for this to be retested!

  7. jponikarchuk commented on May 12, 2025

    @jponikarchuk
    Author

    @CortneyOfstad QA team still can reproduce this issue on build v9.1.43-7

    Retest.61099.mp4
  8. melvin-bot commented on May 13, 2025

    @melvin-bot

    @CortneyOfstad this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  9. 95 remaining items

  10. changed the title [-][$250] Tooltip-Tooltip on the "expense reports" filter is not displayed[/-] [+][Due for payment 2025-07-15] [$250] Tooltip-Tooltip on the "expense reports" filter is not displayed[/+] on Jul 8, 2025
  11. melvin-bot commented on Jul 8, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Jul 8, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.77-2 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-07-15. 🎊

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

    • @getusha requires payment through NewDot Manual Requests
    • @dmkt9 requires payment (Needs manual offer from BZ)
  13. melvin-bot commented on Jul 8, 2025

    @melvin-bot

    @getusha @CortneyOfstad 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]

  14. melvin-bot commented on Jul 15, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @getusha owed $250 via NewDot
    • ROLE: @dmkt9 paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@CortneyOfstad)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1922333040188144414/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. getusha commented on Jul 16, 2025

    @getusha
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 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: N/A We decided on a different expected result and fixed an issue that would have affected every scenario due to the implementation of the Suggested Search feature.

    • [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: N/a

    • [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 one, and we should probably remove the steps in the OP from the test cases we have.

  16. CortneyOfstad commented on Jul 16, 2025

    @CortneyOfstad
    Contributor

    Thanks @getusha!

    @dmkt9 — the job posting unfortunately expired in Upwork, so a new one has been created. I sent you an offer here — https://www.upwork.com/nx/wm/offer/108072549. Please let me know once you accept and i can get that paid ASAP. Thanks!

  17. dmkt9 commented on Jul 16, 2025

    @dmkt9
    Contributor

    @CortneyOfstad Thank you. I have requested on Upwork

  18. garrettmknight commented on Jul 17, 2025

    @garrettmknight
    Contributor

    $250 approved for @getusha

  19. CortneyOfstad commented on Jul 18, 2025

    @CortneyOfstad
    Contributor

    Payment Summary

    @getusha — approved for $250 in ND per comment here
    @dmkt9 – paid $250 via Upwork

    Regression Test

    Not needed per comment here

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions