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
[$250] Expense - Hold message is duplicated after splitting held expense #76005
changed the title [-]Expense - Hold message is duplicated after splitting held expense[/-][+][$250] Expense - Hold message is duplicated after splitting held expense[/+]on Nov 28, 2025
Given this has clear reproduction steps and does not make the user experience much worse, I am taking this our of quality. I will add the task to the canvas for backend engineers so they pick it up
Activity
melvin-bot commentedon Nov 25, 2025
Triggered auto assignment to @RachCHopkins (
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.RachCHopkins commentedon Nov 28, 2025
So the Hold comment (the comment added as a reason when holding) is duplicated.
After Hold:
After Split:
Also the expense history does not note the split. This seems like it's also an issue.
[-]Expense - Hold message is duplicated after splitting held expense[/-][+][$250] Expense - Hold message is duplicated after splitting held expense[/+]melvin-bot commentedon Nov 28, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021994200224543854189
melvin-bot commentedon Nov 28, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (
External)fix: copy only card fields when splitting expenses (Expensify#76005, E…
marufsharifi commentedon Nov 30, 2025
@sobitneupane, @RachCHopkins, is this still open for proposals?
32 remaining items
mountiny commentedon Jan 19, 2026
Given this has clear reproduction steps and does not make the user experience much worse, I am taking this our of quality. I will add the task to the canvas for backend engineers so they pick it up
c3024 commentedon Jan 21, 2026
This is not reproducible anymore for me.
@jponikarchuk
Could you please retest and confirm if this is still reproducible?
jponikarchuk commentedon Jan 21, 2026
@c3024 This issue is not reproducible now
mvtglobally commentedon Jan 24, 2026
Issue not reproducible during KI retests. (First week)
c3024 commentedon Jan 26, 2026
Not reproducible.