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
Split - No bottom margin for date split option #78048
Version Number: v9.2.82-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74652 Email or phone of affected tester (no customers):testpayment935@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Windows 11 pro /Chrome App Component: Money Requests
Action Performed:
Navigate to staging.new.expensify.com
Create workspace and add expense
Go to expense detail page and split the workspace using date ( have at least 10 days apart)
Notice the bottom margin between save button and last split item
Expected Result:
There should be bottom margin between save button and last split item ( Amount and percentage option behavior)
Actual Result:
There is no bottom margin between save button and last split item
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
@ZhenjaHorbach can you post here which PR this came from just so it's documented? again, this isn't a blocker for sure, just curious to link where it came from
@ZhenjaHorbach can you post here which PR this came from just so it's documented? again, this isn't a blocker for sure, just curious to link where it came from
Activity
melvin-bot commentedon Dec 18, 2025
Triggered auto assignment to @bfitzexpensify (
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 Dec 18, 2025
Triggered auto assignment to @Beamanator (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Dec 18, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Dec 18, 2025
💬 A slack conversation has been started in #expensify-open-source
ZhenjaHorbach commentedon Dec 18, 2025
Minor issue
Will fix in the next improvement PR
Beamanator commentedon Dec 18, 2025
I agree this isn't a blocker 👍
Beamanator commentedon Dec 18, 2025
@ZhenjaHorbach can you post here which PR this came from just so it's documented? again, this isn't a blocker for sure, just curious to link where it came from
ZhenjaHorbach commentedon Dec 18, 2025
For the dates feature, we have this PR
garrettmknight commentedon Jan 2, 2026
Fixed! Handling payment in a separate issue.