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
Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist #74445
Personally I think this should work the same regardless of whether the amount is positive or negative, if a user is tracking their own expenses in Expensify then they might want to put in all transaction types
changed the title [-]Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/-][+][HOLD https://github.com/Expensify/Expensify/issues/556957] Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/+]on Nov 21, 2025
changed the title [-][HOLD https://github.com/Expensify/Expensify/issues/556957] Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/-][+]Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/+]on Jan 21, 2026
Activity
mountiny commentedon Nov 11, 2025
@Expensify/product-pr How should we handle this case
melvin-bot commentedon Nov 11, 2025
Triggered auto assignment to @heyjennahay (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Nov 14, 2025
@heyjennahay Whoops! This issue is 2 days overdue. Let's get this updated quick!
mountiny commentedon Nov 19, 2025
@ZhenjaHorbach is this still repro for you?
ZhenjaHorbach commentedon Nov 19, 2025
Partially yes
But it works strangely
That is, by default we don't have selfDM
But if we use the search, it appears
But maybe it's okay
2025-11-19.19.36.03.mov
heyjennahay commentedon Nov 21, 2025
Personally I think this should work the same regardless of whether the amount is positive or negative, if a user is tracking their own expenses in Expensify then they might want to put in all transaction types
mountiny commentedon Nov 21, 2025
I think this might be internim until @jnowakow changes to selfDM are done, then you can use the self dm reportID to create this report always
[-]Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/-][+][HOLD https://github.com/Expensify/Expensify/issues/556957] Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/+]mountiny commentedon Nov 21, 2025
Put it on hold for this https://github.com/Expensify/Expensify/issues/556957 as I think it might help in this situation
14 remaining items
heyjennahay commentedon Jan 7, 2026
Still on hold
heyjennahay commentedon Jan 21, 2026
The PR this is holding on was deployed but I think there are still outstanding items to resolve. @mountiny can you please confirm my understanding?
mountiny commentedon Jan 21, 2026
@jnowakow @MonilBhavsar @ZhenjaHorbach Seems like this was on hold for the selfDM changes, can you retest now that we deployed the changes in BE?
[-][HOLD https://github.com/Expensify/Expensify/issues/556957] Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/-][+]Empty "Choose recipient" screen with useless search after creation expense with negative value when no workspace and selfDM exist[/+]jnowakow commentedon Feb 2, 2026
@mountiny it works for me now:
negative-expense.mov
heyjennahay commentedon Feb 3, 2026
@ZhenjaHorbach do you also want to confirm if you're still experiencing this or whether we can close this out?
mountiny commentedon Feb 4, 2026
Seems like we can close if @jnowakow confirmed this is working for them