Skip to content

[Due for payment 2026-05-07] [$250] Use a larger button for "X selected" on the Reports page to aid discoverability #88176

Closed

Description

@shawnborton

We're finding that a lot of folks select rows (expenses, reports, etc) from the Reports page and miss the green button that allows them to take bulk actions.

Image

As a first step, we'd like to experiment with simply making this button bigger to see if that aids in discoverability.

Image

cc @Expensify/design @Expensify/product

Issue OwnerCurrent Issue Owner: @mallenexpensify
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022046537247697458742
  • Upwork Job ID: 2046537247697458742
  • Last Price Increase: 2026-04-21

Activity

  1. self-assigned this
    on Apr 17, 2026
  2. melvin-bot commented on Apr 17, 2026

    @melvin-bot

    Current assignee @shawnborton is eligible for the NewFeature assigner, not assigning anyone new.

  3. shawnborton commented on Apr 17, 2026

    @shawnborton
    ContributorAuthor

    PR here: #88146

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 17, 2026
  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 17, 2026
  6. melvin-bot commented on Apr 17, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @thelullabyy (External)

  7. melvin-bot commented on Apr 17, 2026

    @melvin-bot

    Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

  8. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 17, 2026
  9. removed
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 21, 2026
  10. 23 remaining items

  11. brunovjk commented on May 1, 2026

    @brunovjk
    Contributor

    No payment is required on my part.

  12. jshaofa-ui commented on May 6, 2026

    @jshaofa-ui

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Users selecting rows on the Reports page frequently miss the green "X selected" bulk action button. The button's current compact size makes it easy to overlook, reducing feature discoverability and causing user frustration.

    What is the root cause of that problem?

    The SearchBulkActionsButton component uses CONST.DROPDOWN_BUTTON_SIZE.SMALL for the bulk action button in wide layouts. This produces a compact pill with limited visual weight — small height, minimal padding, and reduced font size — making it easy to miss against the dense Reports table background.

    The narrow layout uses a separate full-width bottom bar (SearchSelectedNarrow.tsx) which is already prominent, so the issue is isolated to wide layouts.

    What changes do you think we should make in order to solve the problem?

    Primary change: In src/components/Search/SearchBulkActionsButton.tsx, change the buttonSize prop from CONST.DROPDOWN_BUTTON_SIZE.SMALL to CONST.DROPDOWN_BUTTON_SIZE.MEDIUM.

    This single prop change leverages existing design tokens:

    • Button height increases from ~32px to ~40px
    • Padding and font size scale proportionally
    • Chevron icon size increases for better affordance
    • No hardcoded values, fully consistent with the design system

    Additional improvement: Also apply the size increase to the narrow layout button in src/components/Search/SearchSelectedNarrow.tsx for consistency. The narrow layout currently uses a fixed height that could benefit from the same MEDIUM sizing token, ensuring the button is equally discoverable across all viewport widths.

    Files to modify:

    1. src/components/Search/SearchBulkActionsButton.tsx — buttonSize prop: SMALL → MEDIUM
    2. src/components/Search/SearchSelectedNarrow.tsx — align button height with MEDIUM token

    What alternative solutions did you explore?

    1. CONST.DROPDOWN_BUTTON_SIZE.LARGE — Would be even more prominent but risks layout overflow on smaller wide screens. MEDIUM is the safest first step for the experiment.

    2. Adding animation/pulse effect — Could draw more attention but introduces complexity and potential accessibility concerns (motion sensitivity). Better as a follow-up experiment if MEDIUM sizing alone is insufficient.

    3. Increasing margin/spacing around the button — Adds whitespace but doesn't increase the actual interactive target size, which is the core discoverability issue.

    4. Color change — The green color already signals the primary action. Changing it would conflict with the established design language.

  13. melvin-bot commented on May 6, 2026

    @melvin-bot

    📣 @jshaofa-ui! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  14. melvin-bot commented on May 6, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  15. mallenexpensify commented on May 7, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @thelullabyy paid $250 via Upwork.

    @thelullabyy can you please accept the job below? Please reply here and tag me once you have.
    https://www.upwork.com/jobs/~022046537247697458742

  16. melvin-bot commented on May 7, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • 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/2046537247697458742/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
  17. thelullabyy commented on May 8, 2026

    @thelullabyy
    Contributor

    @mallenexpensify Thanks. I accepted the offer

  18. mallenexpensify commented on May 8, 2026

    @mallenexpensify
    Contributor

    @thelullabyy paid, summary updated above. Thx.

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 productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions