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
[Due for Payment 2026-01-16][$250] Split - No spacing between merchant name and input field on Percent tab #78099
Version Number: 9.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):applausetester+khdjdjdjsjsk@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense with long merchant name.
Open the expense report.
Click More > Split.
Go to each tab - Amount, Percent and Date.
Expected Result:
There will be some spacing between merchant name and input field.
Actual Result:
On Percent tab, there is no spacing between merchant name and input field.
👋 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.
changed the title [-][$250] Split - No spacing between merchant name and input field on Percent tab[/-][+][Due for Payment 2026-01-16][$250] Split - No spacing between merchant name and input field on Percent tab[/+]on Jan 12, 2026
[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: N/A
[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 Dec 19, 2025
Triggered auto assignment to @laurenreidexpensify (
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 19, 2025
Triggered auto assignment to @flodnv (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 19, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 19, 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:
31 remaining items
btkcodedev commentedon Jan 8, 2026
PR has been merged
CC: @Pujan92 @flodnv @laurenreidexpensify
Thanks!
[-][$250] Split - No spacing between merchant name and input field on Percent tab[/-][+][Due for Payment 2026-01-16][$250] Split - No spacing between merchant name and input field on Percent tab[/+]mallenexpensify commentedon Jan 12, 2026
Automation failed, updated title and removed
Reviewing.Pujan92 commentedon Jan 16, 2026
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: https://github.com/Expensify/App/pull/48876/files#r1869197328
[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: N/A
[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/App/pull/74652/changes#r2698362148
btkcodedev commentedon Jan 21, 2026
Due date passed, does automation failed again? @Pujan92 ,Please comment if I have to do anything
Thanks!
Pujan92 commentedon Jan 21, 2026
@laurenreidexpensify can you plz help here with the payment
mallenexpensify commentedon Jan 24, 2026
@btkcodedev apologies for the delay, can you please apply for the job
https://www.upwork.com/jobs/~022014854107725191634
Please tag me here once you have
btkcodedev commentedon Jan 24, 2026
Applied @mallenexpensify
Here is my proposal
mallenexpensify commentedon Jan 27, 2026
@btkcodedev can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022014854107725191634
btkcodedev commentedon Jan 28, 2026
@mallenexpensify Accepted!
Thanks!
mallenexpensify commentedon Jan 28, 2026
Payment Summary
Contributor: @btkcodedev paid $250 via Upwork
Contributor+: @Pujan92 due $250 via NewDot
@Pujan92 do we want a test case here?
Pujan92 commentedon Jan 29, 2026
@mallenexpensify I don't think we need a test here.
twisterdotcom commentedon Jan 29, 2026
@Pujan92 has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-c544-a272-95fb-9be2a7626944