Skip to content

[$250] Split - Percentage input field does not expand when percentage is large #78092

New issue
New issue
Closed
Closed
[$250] Split - Percentage input field does not expand when percentage is large#78092
Assignees
puneetlathsonialiapShridharGoeltsa321
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in review

Description

@mitarachim
mitarachim
opened on Dec 19, 2025

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): jsdoijdojnoinjisojsod@gmail.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 of amount 10.00.
  4. Open the expense report.
  5. Click More > Split.
  6. Enter 10000 on any split.
  7. Switch to Percentage.

Expected Result:

Percentage input field will expand when percentage is large.

Actual Result:

Percentage input field does not expand when percentage is large.

On iOS, the amount is split into two lines.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7033272_1766097281132.17.mp4
Image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022002137699890323210
  • Upwork Job ID: 2002137699890323210
  • Last Price Increase: 2026-01-09
  • Automatic offers:
    • tsa321 | Contributor | 110174072
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @sonialiap

Activity

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

  3. melvin-bot commented on Dec 19, 2025

    @melvin-bot
    melvin-botBot
    on Dec 19, 2025 – with Melvin Bot

    Triggered auto assignment to @sonialiap (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.

  4. melvin-bot
    assigned
    puneetlath
    on Dec 19, 2025

  5. melvin-bot commented on Dec 19, 2025

    @melvin-bot
    melvin-botBot
    on Dec 19, 2025 – with Melvin Bot

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

  6. github-actions
    added
    Engineering
    and removed
    DailyKSv2
    on Dec 19, 2025

  7. melvin-bot commented on Dec 19, 2025

    @melvin-bot
    melvin-botBot
    on Dec 19, 2025 – with Melvin Bot

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

  8. github-actions
    added
    HourlyKSv2
    on Dec 19, 2025

  9. github-actions commented on Dec 19, 2025

    @github-actions
    github-actionsBot
    on Dec 19, 2025 – with 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.
  10. lakchote
    removed
    DeployBlockerCashThis issue or pull request should block deployment
    HourlyKSv2
    on Dec 19, 2025

  11. 91 remaining items

  12. melvin-bot commented on Jan 20, 2026

    @melvin-bot
    melvin-botBot
    on Jan 20, 2026 – with Melvin Bot

    📣 @tsa321 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  13. melvin-bot
    removed
    Overdue
    on Jan 20, 2026

  14. tsa321 commented on Jan 21, 2026

    @tsa321
    tsa321
    on Jan 21, 2026
    Contributor

    Thank you, I’ll try to create a PR within one or two days.

  15. melvin-bot
    added
    ReviewingHas a PR in review
    WeeklyKSv2
    and removed
    DailyKSv2
    on Jan 22, 2026

  16. tsa321 commented on Feb 14, 2026

    @tsa321
    tsa321
    on Feb 14, 2026
    Contributor

    Update: The PR was deployed to production seven days ago and this is ready for payment. cc @sonialiap

  17. sonialiap
    added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    DailyKSv2
    and removed
    WeeklyKSv2
    on Feb 17, 2026

  18. sonialiap commented on Feb 17, 2026

    @sonialiap
    sonialiap
    on Feb 17, 2026
    Contributor

    Payment summary:
    @tsa321 $250 paid in upwork ✔️
    @ShridharGoel $250 please request in NewDot and complete the checklist (below)

    Click to expand Checklist 
    # 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:

- [ ] **[Contributor]** If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in [#expensify-open-source](https://app.slack.com/client/E047TPA624F/C01GTK53T8Q) 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:

- [ ] **[Contributor]** If it was decided to create a regression test for the bug, please propose the [regression test](https://github.com/Expensify/App/blob/main/contributingGuides/REGRESSION_TEST_BEST_PRACTICES.md) steps using the template below to ensure the same bug will not reach production again.

<details>
<summary>Regression Test Proposal Template</summary>
<!-- AFTER FILLING THIS OUT, be sure to remove the <details> and <summary> tags from this part of the checklist!!!!! -->

- [ ] **[BugZero Assignee]** Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

    Link to issue:

## Regression Test Proposal
### Precondition:
<!-- List the setup instructions necessary to perform the test -->

-

### Test:
<!-- List the steps that QA should perform -->

1.

Do we agree 👍 or 👎

<!-- AFTER FILLING THIS OUT, be sure to remove the <details> tags!!!!! -->
</details>

  19. ShridharGoel commented on Feb 17, 2026

    @ShridharGoel
    ShridharGoel
    on Feb 17, 2026
    Contributor

    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: N/A

    • [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/Expensify/issues/601080

    Regression Test Proposal

    Test:

    1. Open an expense report.
    2. Click More → Split.
    3. Go to the Amount tab.
    4. Verify the amount text input is left-aligned.
    5. Enter a long number into the amount text input.
    6. Verify the text does not wrap to a second line (the input remains single-line; on iOS, ellipsis … is shown).
    7. Fill both split amounts so the total is less than the original amount.
    8. Verify a warning indicating the total amount is less than the original is displayed at the bottom.
    9. Go to the Percentage tab.
    10. Verify the text input is left-aligned.

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-f916-a57b-acd1-929043cfb7b4
  20. sonialiap
    closed this as completedon Feb 17, 2026
  21. github-project-automation
    moved this to Done in #expensify-bugson Feb 17, 2026

  22. JmillsExpensify commented on Feb 19, 2026

    @JmillsExpensify
    JmillsExpensify
    on Feb 19, 2026
    Contributor

    $250 approved for @ShridharGoel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions