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] [Due for payment 2025-12-19] [Splits in NewDot] Add Split to the select menu when 1 expense is selected, editable and not the child of an existing Split expense #73669
Version Number: N/A Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@coleaeason / @trjExpensify Slack conversation (hyperlinked to channel name): migrate
Action Performed:
Create an expense
Select the checkbox next to the expense (this should work the same in the report view and the Reports page view)
Click 1 selected
Expected Result:
Since you can split in the More menu of an editable, non-split transaction, you should see it in the 1 selected menu as well. There are a few additional pieces of context here:
Submitters and assigned approvers can split expenses that they can edit.
Admins can split expenses on Draft and Processing reports.
Non-editable expenses include pending Expensify Card expenses and Expensiworks expenses for all users.
Users should not see the Split option in the 1 selected menu for portions of expenses that have already been split.
Actual Result:
Split isn't an option in the 1 selected menu.
Workaround:
Users can still open the expense via RHP and split.
Platforms:
Select the officially supported platforms where the issue was reproduced:
ALL
Platforms Tested:
On which of our officially supported platforms was this issue tested:
⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️
Hello everyone, I got the issue from Upwork, checked the repo and the NewDot build, and concluded it can come from the usage of ReportSecondaryActionUtils that has isSplitAction() function
Unless I am wrong, this is where I believed to be the starting problem to trace the issue. As there are some if checks to be done there, I suspect to check it first there
So, if you don't mind:
I can check all of those if checks to make sure everything is working as intended
If that is not the real problem, I can trace to the usage of where isSplitAction() is used in the regarded context and implement fix
If everything that uses isSplitAction() traced and still has the same issue, I may discuss some potential solutions with the core team if needed
This feature was already implemented a few weeks ago 😅
And it will be closed soon
Ah, I see. No worries. Probably I have to ask if the issue is already implemented next time, as I have no clue except a few, but those still need clarification 😁
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NA. This is new feature.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Na
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Oct 28, 2025
Triggered auto assignment to @muttmuure (
NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO. Remember to draft any necessary HelpDot updates by following the instructions here.melvin-bot commentedon Oct 28, 2025
melvin-bot commentedon Oct 28, 2025
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (
NewFeature)garrettmknight commentedon Oct 28, 2025
@dubielzyk-expensify I think this one is pretty simple. Fig here, but:
Reports page:
Report view:
dubielzyk-expensify commentedon Oct 29, 2025
What do you need here sorry? 😅
The green button should say
1 selectedbtwZhenjaHorbach commentedon Oct 30, 2025
@garrettmknight
About Reports page
Do we really need to add Split here?
Since we don't have Merge in this menu also
2025-10-30.14.38.40.mov
40 remaining items
Corfliss commentedon Dec 25, 2025
Contributor details
Your Expensify account email: work@corfliss.io
Upwork Profile Link: https://www.upwork.com/freelancers/~0195762c2c093ab931
melvin-bot commentedon Dec 25, 2025
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
ZhenjaHorbach commentedon Dec 25, 2025
This feature was already implemented a few weeks ago 😅
And it will be closed soon
Corfliss commentedon Dec 25, 2025
Ah, I see. No worries. Probably I have to ask if the issue is already implemented next time, as I have no clue except a few, but those still need clarification 😁
melvin-bot commentedon Dec 31, 2025
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Jan 1, 2026
@eh2077 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
eh2077 commentedon Jan 5, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NA. This is new feature.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Na
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/584454
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-c22f-a6ac-49cc-2dee94021ea4eh2077 commentedon Jan 5, 2026
@mallenexpensify Checklist done, thanks 🙇
lydiabarclay commentedon Jan 5, 2026
Payment Summary
Contributor: @ZhenjaHorbach due $250 via NewDot
Contributor+: @eh2077 due $250 via NewDot
✅ Regression test filed
JmillsExpensify commentedon Jan 8, 2026
$250 approved for @eh2077
garrettmknight commentedon Jan 14, 2026
$250 approved for @ZhenjaHorbach