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
[HOLD] [$250] Remove the "One-expense report" view #63024
We originally introduced the "one-expense report" view with the assumption that:
Expenses would be approved immediately, consistently
Viewing a single expense directly in the report simplified the experience.
Problem
We’ve run into numerous issues and UX inconsistencies:
The majority of our members manually submit reports with multiple expenses.
Delayed/instant submission batches expenses together by default, so there's no way to reliably guarantee one-expense-per-report.
The "one-expense report" view is an on-going source of bugs.
Even internal Expensify employees are often confused. For instance, in the "one-expense report" the total is at the top of the report by necessity, though in the "TradReport" design the total is at the bottom.
On mobile, the supposed benefit of "seeing everything at a glance" doesn’t hold up—opening a one-expense report requires scrolling through a long expense form before you see any details.
"One expense" disrupts our consistent “TradReport” design, which users now expect across the app
CleanShot.2025-05-29.at.10.14.37.mp4
Solution
Remove the "one-expense report" view entirely. This will reduce bugs, simplify maintenance, and unify our app design. What this means in practice:
All reports—whether they contain one expense or many—will share this same layout.
Expenses on the Reports > Expenses view show either a View button or a Review button (when violations present)
I'm curious, in case this task goes through would it mean that the "RHP transaction view" when clicking on transaction row goes away?
I don't think so, no. I think if you are on Reports > Expenses and you click on an expense, each expense should open with just the expense view in the RHP. Does that make sense?
Should I still create a test branch or wait with anything since this was put on HOLD? currently Im waiting.
I commented in Slack but I would still love to see a test branch!
However I focused on not putting a lot of work there, and since single transaction thread logic is spread over many places, there might be some bugs.
But to clean it up properly, means understanding all the edge cases fully - which means spending more time on this.
If something that you would expect to work doesn't - please shout.
What should work and I tested:
in Inbox if you click a preview for report that has only 1 transaction -> you should get table view with 1 expense
if you do the flow: "+" -> Create Report -> you see empty report -> "Create Expense" -> you stay on table view with 1 expense
We still have on-going internal disagreement on this issue, so sadly I'm going to close this out for now. We can revisit down the line though, and I expect we will.
Activity
melvin-bot commentedon May 29, 2025
Current assignee @JmillsExpensify is eligible for the Bug assigner, not assigning anyone new.
JakubKorytko commentedon May 29, 2025
If it is fine to start working on this either tomorrow or on Monday, please assign it to me.
mountiny commentedon May 29, 2025
It might require some backend changes and clean up for sure so happy to help with this one
JmillsExpensify commentedon May 29, 2025
Nice we're set. Thanks!
melvin-bot commentedon May 29, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021928020802640068123
[-]Remove the "One-expense report" view[/-][+][$250] Remove the "One-expense report" view[/+]18 remaining items
shawnborton commentedon Jun 3, 2025
I don't think so, no. I think if you are on Reports > Expenses and you click on an expense, each expense should open with just the expense view in the RHP. Does that make sense?
I commented in Slack but I would still love to see a test branch!
Kicu commentedon Jun 3, 2025
@shawnborton you can use this PR to trigger ad-hoc: #63341
However I focused on not putting a lot of work there, and since single transaction thread logic is spread over many places, there might be some bugs.
But to clean it up properly, means understanding all the edge cases fully - which means spending more time on this.
If something that you would expect to work doesn't - please shout.
What should work and I tested:
shawnborton commentedon Jun 3, 2025
On it!
melvin-bot commentedon Jun 9, 2025
@Kicu Eep! 4 days overdue now. Issues have feelings too...
luacmartins commentedon Jun 9, 2025
On hold for discussions
JmillsExpensify commentedon Jun 11, 2025
Still on hold, @puneetlath is very likely going to pick this up and tweak the solution based on the problem stated above.
JmillsExpensify commentedon Jul 11, 2025
We still have on-going internal disagreement on this issue, so sadly I'm going to close this out for now. We can revisit down the line though, and I expect we will.