Skip to content

[Due for payment 2025-10-31] Expensify Card - No hover effect on chevron icon in Expensify card lists #72565

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.2.30-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #71447
Email or phone of affected tester (no customers): applausetester+bm906@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Web
App Component: Workspace Settings

Action Performed:

Precondition - Expensify Card is enabled, and the admin has assigned a virtual card for himself.

  1. Go to https://staging.new.expensify.com/
  2. Go to Workspace settings > Expensify Card
  3. Hover over the Expensify card list

Expected Result:

Chevron icon should display a hover effect (same as in other clickable chevrons across the app)

Actual Result:

Chevron icon has no hover effect when hovered over, even though it’s clickable and triggers the RHP.
The same issue occurs in the Company cards list.

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

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021978099247279412974
  • Upwork Job ID: 1978099247279412974
  • Last Price Increase: 2025-10-14
Issue OwnerCurrent Issue Owner: @shubham1206agra

Activity

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

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (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 Oct 14, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 14, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 14, 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. 35 remaining items

  7. melvin-bot commented on Oct 24, 2025

    @melvin-bot

    @shubham1206agra / @Krishna2323 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]

  8. melvin-bot commented on Oct 31, 2025

    @melvin-bot

    Issue is ready for payment but no BZ is assigned. @johncschuster you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

  9. johncschuster commented on Nov 3, 2025

    @johncschuster
    Contributor

    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:

    • [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 👎

  10. johncschuster commented on Nov 3, 2025

    @johncschuster
    Contributor

    Payment Summary

    Contributor: @Krishna2323 due $250 via NewDot
    Contributor+: @shubham1206agra due $250 via NewDot

  11. shubham1206agra commented on Nov 3, 2025

    @shubham1206agra
    Contributor

    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: https://github.com/Expensify/App/pull/71447/files#r2487162016

    • [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 Required

    • [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.

    • [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:

    • Expensify and Company Card are enabled, and the admin has assigned a virtual card for himself.

    Test:

    1. Go to Workspace settings > Expensify Card
    2. Hover over the Expensify card list page
    3. Verify the chevron icon opacity is increased
    4. Go to Company card list page
    5. Hover over the Company card list item
    6. Verify the chevron icon opacity is increased

    Do we agree 👍 or 👎

  12. shubham1206agra commented on Nov 6, 2025

    @shubham1206agra
    Contributor

    @johncschuster Can we close this issue?

  13. johncschuster commented on Nov 6, 2025

    @johncschuster
    Contributor

    Sorry for my delay! I was temporarily off the BZ team to focus on an internal project and just re-joined the team! I've posted the QA issue now and will close this up. Don't forget to request payment!

  14. Krishna2323 commented on Nov 6, 2025

    @Krishna2323
    Contributor

    @johncschuster This issue is a follow-up to #71447, so no payment is required here. Thanks!

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.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions