Reports - Unable to sort by Attendees and Per attendee

[lanitochka17]

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.3.52-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: #85332
Email or phone of affected tester (no customers): iipodsnpspnsokpndokpso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• Rules are enabled.
• Attendee tracking is enabled in Rules.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create three expenses with different amount of attendees and different per attendee amount.
4. Go to Reports > Expenses.
5. Click Attendees table title.
6. Click Per attendee table title.

Expected Result:

User can sort expenses by Attendees and Per attendee.

Actual Result:

User is unable to sort expenses by Attendees and Per attendee when Attendees and Per attendee are clickable.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7120702_1775219101717.13.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @nkdengineer

[melvin-bot]

@justinpersaud recently merged #85332, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

[github-actions]

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

[melvin-bot]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #85332 - feat: Person Amount and Attendees in Expense Table by @nkdengineer (High confidence)
Related Issues: 83223

Recommendation: REVERT

PR 85332 added the Attendees and Per attendee columns to the expense table but did not implement sorting support for them, causing the columns to appear sortable while doing nothing when clicked.

Labels: DeployBlockerCash is correctly applied and should remain. No label changes made.

Evidence:

• The issue body and melvin-bot both directly reference PR 85332 as the introducing PR.
• PR 85332 was merged on 2026-04-01 and is listed in the current StagingDeployCash deploy checklist.
• The bug is staging-only (Reproducible in production: N/A - new feature), consistent with the PR only being on staging.

Verification:

• PR 85332 modifies src/components/Search/SearchTableHeader.tsx, adding ATTENDEES and TOTAL_PER_ATTENDEE column configs to getExpenseHeaders() without setting isColumnSortable: false on either one.
• The default when isColumnSortable is omitted is true (SortableHeaderText defaults to true).
• In src/libs/SearchUIUtils.ts, the nonSortableColumns set (line 365) does NOT include ATTENDEES or TOTAL_PER_ATTENDEE, so isColumnSortable() returns true for both -- making them clickable sort headers.
• However, transactionColumnNamesToSortingProperty (line 236) does NOT map either column to a transaction sort property, and getSortedTransactionData() has no special-case handlers for them.
• When a user clicks either column header, sortingProperty resolves to undefined at line 3393, and the function returns data unsorted immediately.

Root Cause:
The PR added the two new columns to the table header but did not add them to nonSortableColumns (to disable sorting) nor implement sort comparators in getSortedTransactionData. The columns render as interactive/sortable headers but clicking them has no effect. The fix is to either add isColumnSortable: false to both header configs plus add them to nonSortableColumns, or implement proper sort logic for them.