You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-05-13] [$250] Attendees are not copied in alphabetical order when they are arranged alphabetically #89130
Version Number: 9.3.64-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#87705 Email or phone of affected tester (no customers):sdsodijnosdjoij@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.2 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Enable Rules in workspace settings.
Enable Attendee tracking in Rules.
Go to staging.new.expensify.com
Go to workspace chat.
Click + > Create expense > Manual.
Enter amount > Next.
On confirm page, click Attendees.
Add "banana", then add "apple".
Click Create expense.
Create one more expense (no need add attendee).
Open the report.
Bulk select both expenses.
Click dropdown button > Merge.
Select the 3 attendees in Attendees section, then select any for other sections.
Click Continue.
On confirm page, hover over Attendees field and click Copy button.
Close the RHP.
Paste the content.
Expected Result:
Attendees will be copied in alphabetical order because they are arranged alphabetically on confirm page.
Actual Result:
Attendees are not copied in alphabetical order when they are arranged alphabetically on confirm page.
Copied attendees - banana, apple
Attendees on confirm page - apple, banana
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #87705 - "feat: user pill workflow attendees" by @TaduJR (High confidence) Related Issues: #84985
Recommendation: REVERT
PR #87705 introduced the bug by applying sortAlphabetically() only to the visual UserPills display component, while leaving the attendeesCopyValue derived from the original unsorted actualAttendees array. Since the fix is non-trivial (requires ensuring the sort is applied consistently to both the display and copy paths) and the change is a UI enhancement rather than a critical bug fix, a revert is the safest path.
Assigned: @TaduJR (PR author), @nyomanjyotisa and @Gonals (approving reviewers) Labels: DeployBlockerCash kept (frontend App PR caused the bug). DeployBlocker is not present and should not be added.
Detailed Analysis
Evidence
The issue is staging-only (not reproducible in production), version 9.3.64-0, matching the staging deploy window for PR feat: user pill workflow attendees #87705 which merged on 2026-04-27.
The bug is in the "Copy" button on the attendees field of the expense confirm page: displayed pills are sorted alphabetically, but the copied text is not.
attendeesCopyValue is derived directly from getAttendeesTitle, so the Copy button produces the original insertion order instead of the sorted alphabetical order shown on screen.
The same pattern exists in AttendeeField.tsx (used on the confirmation page before submission), where the UserPillstitleComponent also sorts via sortAlphabetically, but no sorted copy value is provided.
Root Cause
PR #87705 replaced the plain title prop (a comma-separated string) with a titleComponent rendering UserPills. The UserPills component sorts the attendees alphabetically for display. However, the copyValue prop passed to MenuItemWithTopDescription is sourced from attendeesCopyValue, which is built from the original unsorted actualAttendees array. The display order and the clipboard content are now computed from two different orderings, causing the mismatch.
@nyomanjyotisa 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]
Activity
melvin-bot commentedon Apr 28, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #87705
melvin-bot commentedon Apr 28, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 28, 2026
👋 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:
OSBotify commentedon Apr 28, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #87705 - "feat: user pill workflow attendees" by @TaduJR (High confidence)
Related Issues: #84985
Recommendation: REVERT
PR #87705 introduced the bug by applying
sortAlphabetically()only to the visualUserPillsdisplay component, while leaving theattendeesCopyValuederived from the original unsortedactualAttendeesarray. Since the fix is non-trivial (requires ensuring the sort is applied consistently to both the display and copy paths) and the change is a UI enhancement rather than a critical bug fix, a revert is the safest path.Assigned: @TaduJR (PR author), @nyomanjyotisa and @Gonals (approving reviewers)
Labels:
DeployBlockerCashkept (frontend App PR caused the bug).DeployBlockeris not present and should not be added.Detailed Analysis
Evidence
9.3.64-0, matching the staging deploy window for PR feat: user pill workflow attendees #87705 which merged on 2026-04-27.StagingDeployCashchecklist.Verification
Affected file:
src/components/ReportActionItem/MoneyRequestView.tsxPR #87705 modifies this file (confirmed via
gh pr view 87705 --json files).The specific change that introduced the bug:
titleComponentnow renders<UserPills users={sortAlphabetically(...)} />— so the displayed pills are sorted.getAttendeesTitle(line 811) is still computed as:attendeesCopyValueis derived directly fromgetAttendeesTitle, so the Copy button produces the original insertion order instead of the sorted alphabetical order shown on screen.The same pattern exists in
AttendeeField.tsx(used on the confirmation page before submission), where theUserPillstitleComponentalso sorts viasortAlphabetically, but no sorted copy value is provided.Root Cause
PR #87705 replaced the plain
titleprop (a comma-separated string) with atitleComponentrenderingUserPills. TheUserPillscomponent sorts the attendees alphabetically for display. However, thecopyValueprop passed toMenuItemWithTopDescriptionis sourced fromattendeesCopyValue, which is built from the original unsortedactualAttendeesarray. The display order and the clipboard content are now computed from two different orderings, causing the mismatch.arosiclair commentedon Apr 28, 2026
This is super minor. Demoting
31 remaining items
melvin-bot commentedon May 6, 2026
@nyomanjyotisa 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]
melvin-bot commentedon May 12, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)nyomanjyotisa commentedon May 13, 2026
I don't think we should handle payment here, since we already discussed it in the original issue
melvin-bot commentedon May 13, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
melvin-bot commentedon May 18, 2026
@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon May 20, 2026
@mallenexpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon May 22, 2026
@mallenexpensify 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
mallenexpensify commentedon May 22, 2026
Closing per the above.