Skip to content

[Due for Payment 2026-01-16][$250] Split - No spacing between merchant name and input field on Percent tab #78099

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense with long merchant name.
  4. Open the expense report.
  5. Click More > Split.
  6. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Bug7033415_1766121690177.21.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022002055459487440650
  • Upwork Job ID: 2002055459487440650
  • Last Price Increase: 2025-12-19
Issue OwnerCurrent Issue Owner: @

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Dec 19, 2025
  2. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    Triggered auto assignment to @flodnv (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Dec 19, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. 31 remaining items

  7. btkcodedev commented on Jan 8, 2026

    @btkcodedev
    Contributor

    PR has been merged
    CC: @Pujan92 @flodnv @laurenreidexpensify
    Thanks!

  8. 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
  9. mallenexpensify commented on Jan 12, 2026

    @mallenexpensify
    Contributor

    Automation failed, updated title and removed Reviewing.

  10. Pujan92 commented on Jan 16, 2026

    @Pujan92
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • [] 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
  11. btkcodedev commented on Jan 21, 2026

    @btkcodedev
    Contributor

    Due date passed, does automation failed again? @Pujan92 ,Please comment if I have to do anything
    Thanks!

  12. Pujan92 commented on Jan 21, 2026

    @Pujan92
    Contributor

    @laurenreidexpensify can you plz help here with the payment

  13. mallenexpensify commented on Jan 24, 2026

    @mallenexpensify
    Contributor

    @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

  14. btkcodedev commented on Jan 24, 2026

    @btkcodedev
    Contributor

    Applied @mallenexpensify
    Here is my proposal

  15. mallenexpensify commented on Jan 27, 2026

    @mallenexpensify
    Contributor

    @btkcodedev can you please accept the job below? Please reply here and tag me once you have.
    https://www.upwork.com/jobs/~022014854107725191634

  16. btkcodedev commented on Jan 28, 2026

    @btkcodedev
    Contributor

    @mallenexpensify Accepted!
    Thanks!

  17. mallenexpensify commented on Jan 28, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @btkcodedev paid $250 via Upwork
    Contributor+: @Pujan92 due $250 via NewDot

    @Pujan92 do we want a test case here?

  18. Pujan92 commented on Jan 29, 2026

    @Pujan92
    Contributor

    @mallenexpensify I don't think we need a test here.

  19. twisterdotcom commented on Jan 29, 2026

    @twisterdotcom
    Contributor

    @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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions