Skip to content

Consistent checkboxes and radio buttons UI#87087

Open
mhawryluk wants to merge 92 commits intoExpensify:mainfrom
software-mansion-labs:@zfurtak/reapply-ui-consistency
Open

Consistent checkboxes and radio buttons UI#87087
mhawryluk wants to merge 92 commits intoExpensify:mainfrom
software-mansion-labs:@zfurtak/reapply-ui-consistency

Conversation

@mhawryluk
Copy link
Copy Markdown
Contributor

@mhawryluk mhawryluk commented Apr 3, 2026

Explanation of Change

This is a second attempt at bringing consistency to selection lists checkboxes and radio buttons after the the first PR was reverted: #83799

Now all multiple selection lists get square checkboxes, while single selection lists show the radio buttons with new styles. Initially focused items should not be highlighted like they are when they're hovered/ focused with the keyboard.

Apart from the visual consistency, this PR also aims to refactor the related code. It introduces a unified SelectionButton component that renders as either a checkbox or radio button based on a role prop, replacing several different selection indicators. Checkbox and RadioButton are now thin wrappers around it. For SelectionLists selection button rendering has been moved in new into SelectableListItem wrapper accepting a selectionButtonPosition prop, so most individual list item components (and BaseListItem) no longer implement their own selection UI.

Key changes:

  • RadioListItem renamed to BaseSelectListItem - serves as the shared base for SingleSelectListItem and MultiSelectListItem, which no longer manually create checkbox components.
  • Simplified SelectionScreen - always uses SingleSelectListItem now, the listItem prop was removed
  • Removed SelectCircle, SingleOptionSelector and the Search-specific CardListItem. All usages replaced with RadioButton or the standard selection list patterns.
  • The shouldUseNewStyle prop on RadioButton has been removed, the new style is now the only style.
  • Introduced SelectableListItem - a new intermediary layer between BaseListItem and all individual list items that show a selection button. This is where selection button rendering now lives, keeping BaseListItem completely free of selection concerns.
  • Added BareUserListItem - a display variant of UserListItem that uses BaseListItem directly (no selection button ever rendered).
Before After

Fixed Issues

$ #74938
PROPOSAL: N/A

Tests

Simplified testing cases to test one example of each kind:

  1. SingleSelectListItem: Profile > Preferences > Language
  2. MultiSelectListItem: Reports (Spend) > Filters > Has
  3. TableListItem: Workspace > Members (long-press to enter multi-select)
  4. UserListItem: Chat "+" > Assign task > Next > Assignee
  5. BareUserListItem: Global "+" > Start Chat
  6. UserSelectionListItem: Search > Filters > From
  7. CardListItem: Search > Filters > Card
  8. InviteMemberListItem: Workspace > Members > Invite member
  9. TravelDomainListItem: Settings > Travel > domain selector (requires travel enabled)
  10. RadioButtons: Settings > Subscription > Cancel > survey
  11. ReportCardLostPage: Settings > Wallet > Expensify Card > Report card lost/damaged
  12. SubscriptionPlanCard: Settings > Subscription > compare plans
  13. Onboarding Accounting page: Onboarding flow > Accounting integration selection
  14. MenuItem with RadioButton: Workspace > Categories > Import spreadsheet > the column header dropdowns

Bugs that caused the recent revert

  • Account > Wallet > Enable Wallet > Add bank account > Go through Plaid flow > Next button on Choose your bank account page will have left and right spacing.
  • Workspace settings > Workflows > Payer under Payments section > The selected payer will show radio button on the right side.
  • (at least two workspaces with per diem rates required) FAB > Create expense > Per diem > Select any workspace > Click RHP back button > The selected workspace will show radio button on the right side.
  • Navigate to reports page > Tap on dates filter > There is a correct margin between the date filters
  • Workspace chat. > Create a manual expense. > Open the just created expense. > Click on "More" > "Change Workspace" > radio button is present next to workspaces and that actual workspace has it selected > Select another workspace to move the expense to.
  • FAB > Create expense > Manual. > Enter amount > Next. > Select a participant. > On confirm page, click To field. > The list will show the participant as selected.
  • Click search button. > Type anything > Highlight on the selection is not cut off.
  • Reports (Spend) > Reports > Click Type quick filter. > Click Status quick filter. > Type options will have the same paddings as Status options.

Full testing cases:

Single selection list

For each of the following pages verify:

  • every item has a radio style button on the right hand side
  • radio button has dimensions of 20x20px
  • initially selected item has radio checkmark selected
  • initially selected item does not have any background highlight
  • each item which is not disabled is highlighted on mouse hover and the mouse cursor is of pointer style.
Reports
  • Filter dropdown buttons with popups:
    • Filters > type
    • Filters > action
    • Filters > approved
    • Filters > billable
    • Filters > date
    • Filters > exported
    • Filters > paid
    • Filters > posted
    • Filters > reimbursable
    • Filters > submitted
    • Filters > withdrawal type
    • Filters > withdrawn
Workspace
  • Overview

    • default currency
    • company address > country
    • company address > state (select country = US to see this option)
    • more > transfer owner > currency
  • Members

    • member > role
  • Reports

    • add field > type
    • add field > initial value (only for type = list)
  • Accounting - QBO

    • import > classes > displayed as
    • import > customers/projects > displayed as
    • import > locations > displayed as
    • export > preferred exporter
    • export > export out-of-pocket expenses as > export as
    • export > export out-of-pocket expenses as > account
    • export > export company card expenses as > export as
    • export > export company card expenses as > account
    • export > export company card expenses as > default vendor
    • card reconciliation > reconciliation account
  • Accounting - QBD

    • import > classes > displayed as
    • import > customers/projects > displayed as
    • export > preferred exporter
    • export > export date
    • export > export out-of-pocket expenses as > export as
    • export > export out-of-pocket expense as > account
    • export > export invoices to
    • export > export company card expenses as > export as
    • export > export company card expenses as > credit card account
  • Accounting - Xero

    • xero organization
    • import > tracking categories > all map xero [...] to options
    • export > preferred exporter
    • export > purchase bill date
    • export > purchase bill status
    • export > xero bank account
    • card reconciliation > reconciliation account
    • advanced > auto sync > when to export
    • advanced > xero bill payment account
    • advanced > xero invoice collection account
  • Accounting - NetSuite

    • subsidiary
    • import > departments
    • import > classes
    • import > locations
    • import > customers/projects > toggle either of the options > display as
    • import > custom segment/records > add custom segment record > do you want to add a custom segment or a custom record - page
    • import > custom segment/records > add custom segment record > ... > How should this custom record be displayed in Expensify - page
    • import > custom segment/records > item > displayed as
    • import > custom lists > add custom list > name
    • import > custom lists > add custom list > ... > How should this custom list be displayed in Expensify - page
    • import > custom lists > item > displayed as
    • export > preferred exporter
    • export > export date
    • export > export out-of pocket expenses as > export as
    • export > export company card expense as > export as
    • export > export company card expense as > default vendor
    • export > export invoices to
    • export > invoice item
    • export > invoice item = select existing > invoice item
    • export > journal entries tax posting account
    • card reconciliation > reconciliation account
    • advanced > auto-sync > when to export
    • advanced > reimbursement account
    • advanced > collection account
    • advanced > expense report approval level
    • advanced > vendor bill approval level
    • advanced > A/P approval level
  • Accounting - Sage Intacct

    • entity
    • import > departments > displayed as
    • import > classes > displayed as
    • import > locations > displayed as
    • import > customers > displayed as
    • import > projects (jobs) > displayed as
    • import > user-defined dimensions > add user-defined dimension
    • import > item
    • export > preferred exporter
    • export > export date
    • export > export out-of pocket expenses as > export as
    • export > export out-of pocket expenses as > default vendor
    • export > export company card expense as > export as
    • export > export company card expense as > credit card account
    • export > export company card expense as > default vendor
    • card reconciliation > reconciliation account
    • advanced > auto-sync > when to export
    • advanced > sage intacct payment account
  • Categories

    • more > settings > all default category options
    • category > approver
    • category > default tax rate
    • category > flag amount over > type
    • category > require receipts over
    • more > Import spreadsheet > Choose file > Dropdown buttons with popups
  • Tags

    • tag > approver
  • Taxes

    • more > settings > workspace currency default
    • more > settings > foreign currency default
  • Workflows

    • submission frequency (enable delay submissions toggle to see this option)
    • workflow > approver (enable add approvals toggle to see this option)
    • workflow > additional approver
    • payer (enable make or track payments toggle and add a bank account to see this option)
  • Rules

    • cash expense default
    • billable default
  • Distance rates

    • settings > unit
    • settings > default category
  • Expensify cards

    • issue card > who needs a card
    • issue card > choose a limit
    • more > settlement account
    • more > settlement frequency
    • card > limit type
  • Company cards

    • add cards > country
    • add cards > select feed type step
    • add cards > select feed type step (select direct feed) > who's your bank
    • add cards > select feed type step (select commercial feed) > who's your card provider
    • card > [accounting software name] credit card export
    • select cards feed
    • settings > settlement close date
    • settings > settlement close date = custom day of month > custom close date
    • assign card > who needs a card
    • assign card > choose a card
    • assign card > choose a transaction start date
  • Per diem

    • more > settings > default category
    • rate > currency
Account
  • Profile

    • status > clear after
    • status > vacation delegate
    • pronounce
    • timezone
    • date of birth > year
    • address > country
    • address > state (select country = US to see this option)
  • Subscription

    • add payment card > currency
    • request early cancellation
    • subscription settings > disable auto renew
    • Your plan > Explore all plans
  • Wallet

    • add bank account > country
    • add bank account > country (select any other than US) > currency
    • Enable Payments > add bank account > Plaid step > choose an account (RadioButtons after Plaid link completes)
    • Enable Payments > Idology questions (identity verification multiple-choice;
    • click on an Expensify Card > Report card lost or damaged > Why do you need a new card?
  • Expense rules

    • new rule > category
    • new rules > tag
    • new rule > tax
    • new tule > reimbursable
    • new rule > billable
  • Preferences

    • priority mode
    • language
    • payment currency
    • theme
  • Security

    • add copilot > select copilot
    • add copilot > access level
    • copilot > three dot menu > change access level
FAB
  • Create expense

    • manual > currency
    • manual > enter amount > choose recipient
    • manual > confirmation page > category
    • manual > confirmation page > date > year
    • manual > confirmation page > tag
    • manual > confirmation page > tax
    • manual > confirmation page > report
    • distance > confirmation page > rate
    • per diem > country
    • per diem > select country > add time > sub-rate
  • Create report > choose workspace

  • Start chat

    • room > workspace
    • room > who can post
    • room > visibility
Chat
  • Tracked expense

    • submit to someone > choose recipient
  • Workspace expense

    • expense item > report field (workspace should have at least one list type report field)
    • expense item > category
    • expense item > tag
    • expense item > tax
    • expense item > report
    • expense item > rate (for distance expense item only)
    • expense report > more > change workspace
    • expense report > more > change approver (only workspace admins and owner could see this option)
  • create task > assignee

  • task > assignee

  • room chat

    • Room chat > details > settings > notify me about new messages
    • details > settings > who can post
    • details > settings > visibility
  • Expense report > details > export (workspace must have an accounting connection; I only managed to access it via url: r/<reportID>/details/export/intacct)

  • Transaction Merge

    • Choose transaction to merge with (radio button on transaction item rows)
    • Receipt selection (choose which receipt to keep)
    • Field-by-field duplicate resolution (choose value from transaction A vs B for each conflicting field)
  • Add unreported expense to report

Onboarding
  • track and budget expenses > name > create workspace > default currency
  • manage my team > how many employees do you have?
  • manage my team > 1-10 > do you use any accounting software
Search router (the top right magnifying glass icon)
  • No selection buttons.
  • Initially selected item is highlighted.
  • The highlight is not cut off at any point.

Multi selection

For each of the following pages verify:

  • Item has a checkbox style button on the right hand side
  • The checkmark has dimensions of 20x20px
  • Initially selected items have checkmarks selected
  • Initially selected items do not have any background highlight
  • Each item which is not disabled is highlighted on mouse hover and the mouse cursor is of pointer style.
Reports
  • Filter dropdown buttons
    • Filters > from
    • Filters > has
    • Filters > status
    • Filters > to
    • Filters > workspace
    • Filters > card
    • Filters > category
    • Filters > currency
    • Filters > expense type
    • Filters > purchase currency
    • Filters > tag
    • Filters > tax rate
    • Filters > type = chat
    • Filters > in
    • filters > is
    • Filters > type = task
    • Filters > assignee
  • Display dropdown buttons and RHP
    • Display > Sort by
    • Display > Group by
    • Display > Edit columns
Workspace
  • Overview
    • more > invite
  • Members
    • the table of members (for admins, on narrow view after long press > select, no button otherwise)
    • invite member
  • Workflows
    • workflow > expense from
FAB
  • Create expense
  • manual > confirmation page > Attendees
Onboarding
  • track and budget expenses > name > create workspace > continue > invite members
  • manage my team > 1-10 > do you use any accounting software > interested features

No selection button

  • Workspace > Categories > More > Settings > the list under Default spend categories
  • Open an expense > More > Split > the split items
  • IOU > Confirmation Page > To section
  • Workspace > Receipt partners > Manage invites
  • Settings > Wallet > Bank account three dot menu
  • Onboarding > Suggested workspaces to join

Offline tests

N/A

QA Steps

Same as tests.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Nagranie.z.ekranu.2026-04-21.o.15.56.43.mov

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 3, 2026

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 7, 2026

mhawryluk added 10 commits April 7, 2026 12:07
…nents

- Removed the `NEW_CHAT` constant from `src/CONST/index.ts`.
- Cleaned up `radioButtonStyle` references in various components, replacing them with consistent styles.
- Added `accessible` prop to `Checkbox` and `RadioButton` components for better screen reader support.
- Updated several list item components to use `shouldShowRadioButton` instead of `shouldUseDefaultRightHandSideCheckmark` for clarity.
- Removed unnecessary props and improved overall code readability across multiple files.
@dukenv0307
Copy link
Copy Markdown
Contributor

on it now

@dukenv0307
Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-04-22.at.22.46.50.mov
Android: mWeb Chrome
Screen.Recording.2026-04-22.at.22.34.49.mov
iOS: HybridApp
Screen.Recording.2026-04-22.at.22.39.30.mov
iOS: mWeb Safari
Screen.Recording.2026-04-22.at.22.33.09.mov
MacOS: Chrome / Safari
Screen.Recording.2026-04-22.at.22.30.20.mov

@github-actions
Copy link
Copy Markdown
Contributor

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@grgia
Copy link
Copy Markdown
Contributor

grgia commented Apr 23, 2026

QA regression suite requested @mhawryluk https://expensify.slack.com/archives/C09V78U42D8/p1776934666001219

@jponikarchuk
Copy link
Copy Markdown

Invoice - Hidden appears on participant list after selecting non-existing email

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): sdjinisjoijodsjoidsjnio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

Precondition:

  • Enable Invoices in workspace settings.
  1. Go to https://87087.pr-testing.expensify.com/
  2. Open FAB > Send invoice.
  3. Enter amount > Next.
  4. Enter non-existing Gmail account.
  5. Select the user.
  6. On confirm page, click To field.

Expected Result:

Hidden will not appear on participant list.

Actual Result:

Hidden appears on participant list after selecting non-existing email.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@jponikarchuk
Copy link
Copy Markdown

Expense - Non-functional radio button on details selection step when reviewing duplicates

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): sdjinisjoijodsjoidsjnio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create two expenses with same amount and merchant., but different category.
  4. Open the report.
  5. Click Review duplicates.
  6. Select any category and proceed to confirm page.
  7. Click RHP back button.

Expected Result:

Radio button should not appear on expense details selection step since it never shows the selection.

Actual Result:

Radio button appears on expense details selection step when it never shows the selection.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@jponikarchuk
Copy link
Copy Markdown

Expense - Hidden and self DM are both selected after selecting self DM

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): sdjinisjoijodsjoidsjnio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Go to https://87087.pr-testing.expensify.com/
  2. Open FAB > Create expense > Manual.
  3. Enter amount > Next.
  4. On confirm page, click To field.
  5. Select self DM.
  6. Click To field.

Expected Result:

Hidden will not appear after selecting self DM.

Actual Result:

Hidden and self DM are both selected after selecting self DM.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@mitarachim
Copy link
Copy Markdown

Copilot - Radio button never marks copilot as selected

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): sdjinisjoijodsjoidsjnio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to Profile > Security.
  3. Click Add copilot.
  4. Select any user > Next.
  5. Click RHP back button.

Expected Result:

Radio button should mark the user as selected.

Actual Result:

Radio button never marks copilot as selected.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7136619_1776949696502.4.mp4

@jponikarchuk
Copy link
Copy Markdown

Copilot - New radio button is not applied in account switcher

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: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): sdjinisjoijodsjoidsjnio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

Precondition:

  • User is a copilot of another account.
  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to Account.
  3. Click account switcher.

Expected Result:

The new radio button will be applied in account switcher.

Actual Result:

The new radio button is not applied in account switcher.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Screenshot

@mitarachim
Copy link
Copy Markdown

Bank - "Please select an option to proceed" does not have left margin

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): applausetester+sdoinsdjoisjd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to workspace settings > Workflows.
  3. Click Add bank account > Log into your bank.
  4. Complete Plaid flow.
  5. On Choose an account page, click Next button without selecting account.

Expected Result:

"Please select an option to proceed" will have left margin.

Actual Result:

"Please select an option to proceed" does not have left margin.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7136632_1776950409801!Screenshot_2026-04-23_at_21 18 11
Bug7136632_1776950409799.6.mp4

@jponikarchuk
Copy link
Copy Markdown

Bank - Radio button in Industry classification code list is never marked

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): applausetester+sdoinsdjoisjd@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to workspace settings > Workflows.
  3. Click Add bank account > Log into your bank.
  4. Complete Plaid flow.
  5. Proceed to Step 5 - Which industry is the business classified under?
  6. Select any option.

Expected Result:

The radio button in Industry classification code list should be functional, or it should stay hidden because it never appears marked.

Actual Result:

The radio button in Industry classification code list is never marked.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@jponikarchuk
Copy link
Copy Markdown

Workspace Plan - Workspace is created with a default control plan type

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: macOS chrome

Action Performed:

  1. Sign in with a new account
  2. Create a workspace > Change the plan type to Control
  3. Create a second workspace
  4. Open the workspace overview page

Expected Result:

The default plan type should be Collect

Actual Result:

The default plan type for the second workspace is Control

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@mitarachim
Copy link
Copy Markdown

Expensify Card - Edit spend rules button is not responsive

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): applausetester+sdoinsdjoisjd@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

Precondition:

  • Workspace is set up with Expensify Card feature.
  • Assign a virtual card to yourself.
  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to workspace settings > Expensify Card.
  3. Click on the card.
  4. Click Edit spend rules.

Expected Result:

Edit spend rules button should be responsive.

Actual Result:

Edit spend rules button is not responsive.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7136674_1776954885320.8.mp4

@unzig21
Copy link
Copy Markdown

unzig21 commented Apr 23, 2026

Workspace - Selected member is highlighted when focused with keyboard

Version Number: 9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): negasofonias@gmail.com
Issue reported by: Applause Internal Team
Device used: WIndows 10/Chrome

Action Performed:

  1. Go to a workspace and add few members
  2. Select one of the new memebers
  3. Using keyboard arrow focus on selected member and observe the member is highlighted

Expected Result:

Focused selections should not be highlighted again

Actual Result:

Using keyboard arrow focus on selected member and observe the member is highlighted

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7136643_1776951719343.bandicam_2026-04-23_16-30-55-266.mp4

@lanitochka17
Copy link
Copy Markdown

lanitochka17 commented Apr 23, 2026

Track Expense - Hidden user is displayed after choosing Submit it to someone

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-21836/folder/13176877/41237352/1362524681
Email or phone of affected tester (no customers):
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Create a new account without workspace
  2. Go to self DM
  3. Click on the "+" button next to composer
  4. Create a track expense
  5. Click on the "Submit it to someone" button

Expected Result:

Info message to submit an expense should be displayed in RHP after selecting "Submit it to someone" option.

Actual Result:

A selected hidden user is displayed in RHP when selecting the "Submit it to someone" option.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7136699_1776956996332.ExpensifyHiddenOnRHP.mp4

@jponikarchuk
Copy link
Copy Markdown

Radio button displayed but not selected when sharing images

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): applausetester+abr883@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Android, IOS

Action Performed:

  1. Open the device Gallery.
  2. Select an image.
  3. Tap Share.
  4. Choose the Expensify app.
  5. Select any user.

Expected Result:

The radio button should either be properly selected or not displayed at all on the share-to-Expensify screen after selecting user

Actual Result:

A radio button is displayed but not selected.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@jponikarchuk
Copy link
Copy Markdown

Company cards - All cards dropdown list is scrollable

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): applausetester+sdoinsdjoisjd@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: undefined
Device used: Mac 26.2 / Chrome
App Component: undefined

Action Performed:

Precondition:

  • Add a direct feed on workspace settings > Company cards.
  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to workspace settings > Company cards.
  3. Click All cards dropdown.

Expected Result:

All cards dropdown list should not be scrollable, similar to staging and production.

Actual Result:

All cards dropdown list is scrollable.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

@jponikarchuk
Copy link
Copy Markdown

jponikarchuk commented Apr 23, 2026

Company cards - "American Express Corporate Cards" is truncated

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): sdjinisjoijodsjoidsjnio@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to workspace settings > Company cards.
  3. Click Add cards > Add cards.
  4. Select any country > Next.
  5. Select Commercial feed > Next.

Expected Result:

"American Express Corporate Cards" will not be truncated (or display long name in two lines).

Actual Result:

"American Express Corporate Cards" is truncated.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bandicam.2026-04-23.20-02-11-034.mp4

Copy link
Copy Markdown
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mhawryluk could you check the regression case for Disabled rows with checkboxes. I think the old behavior showed a (disabled) checkbox on disabled invite-list rows when multi-select was on.

@jponikarchuk
Copy link
Copy Markdown

Report field - Radio button is not marked, checkmark is shown next to radio button

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory
Email or phone of affected tester (no customers): applausetester+sdoinsdjoisjd@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.2 / Chrome

Action Performed:

Precondition:

  • Add a list type report field with at least one initial value in workspace settings > Reports.
  1. Go to https://87087.pr-testing.expensify.com/
  2. Go to workspace chat.
  3. Create a report.
  4. Open the report.
  5. Click on the list report field.

Expected Result:

Radio button will be marked as selected.

Actual Result:

Radio button is not marked as selected. Checkmark is shown next to the radio button.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

https://github.com/user-attachments/assets/a9f1e658-c684-44d4-add9-4f067e5600c7
Screenshot

@jponikarchuk
Copy link
Copy Markdown

Login - #admins room tasks are not displayed after sign in

Version Number: v9.3.61-3 PR:87087
Reproducible in staging?: No
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176924/test-cases/41237572
Email or phone of affected tester (no customers): useronboarding@onboarding32321211.com
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome, iOS 13 / iPhone 26.3

Action Performed:

  1. Create a new account on NewDot with the following format - useronboarding@onboarding[unique numer].com
  2. Select "Manage my team's expenses"
  3. Select the option of "5-10 employees" and click continue
  4. Select any accounting option (other than none) and continue
  5. Navigate to #admins room if not redirected automatically

Expected Result:

Tasks should be visible in #admins room

Actual Result:

Tasks don't appear in #admins room

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants