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.24-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A
Email or phone of affected tester (no customers): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: N/A
Issue reported by: Internal
Slack conversation: https://expensify.slack.com/archives/C03U7DCU4/p1771522356898249
Action Performed:
- Create a workspace expense.
- Add multiple attendees to the expense.
- Split the expense between attendees.
- View the expense in the NewDot expense table.
Expected Result:
When an expense is split between multiple attendees, the per-person amount should be clearly displayed in the expense table (e.g., “£11.75 per person”), similar to Classic.
Additionally, attendees should eventually be represented in a dedicated column (e.g., avatars in an “Attendees” column), while maintaining a clean and consistent table layout aligned with NewDot design principles.
This should be accomplished by adding two new columns. Attendees and Amount per attendee:
Tooltips:
- standard user tooltip when hovering over a single user
- text-only tooltip when hovering over the +X
Custom columns in reports are coming here: #82252. These new columns should be visible in reports as well as in the reports page.
Actual Result:
The expense table only displays the total amount. The per-person split amount is not shown, making it less clear how much each attendee is responsible for and how category limits apply.
Workaround:
Users can open the expense details page to manually calculate or review the split amounts. Expensify can still be used without this being fixed, but clarity is reduced when reviewing split expenses.
Platforms:
Select the officially supported platforms where the issue was reproduced:
Screenshots/Videos
View all open jobs on GitHub
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022025995963017033332
- Upwork Job ID: 2025995963017033332
- Last Price Increase: 2026-03-02
Issue Owner
Current Issue Owner: @mallenexpensify
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.24-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A
Email or phone of affected tester (no customers): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: N/A
Issue reported by: Internal
Slack conversation: https://expensify.slack.com/archives/C03U7DCU4/p1771522356898249
Action Performed:
Expected Result:
When an expense is split between multiple attendees, the per-person amount should be clearly displayed in the expense table (e.g., “£11.75 per person”), similar to Classic.
Additionally, attendees should eventually be represented in a dedicated column (e.g., avatars in an “Attendees” column), while maintaining a clean and consistent table layout aligned with NewDot design principles.
This should be accomplished by adding two new columns.
AttendeesandAmount per attendee:Tooltips:
Custom columns in reports are coming here: #82252. These new columns should be visible in reports as well as in the reports page.
Actual Result:
The expense table only displays the total amount. The per-person split amount is not shown, making it less clear how much each attendee is responsible for and how category limits apply.
Workaround:
Users can open the expense details page to manually calculate or review the split amounts. Expensify can still be used without this being fixed, but clarity is reduced when reviewing split expenses.
Platforms:
Select the officially supported platforms where the issue was reproduced:
Screenshots/Videos
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mallenexpensify