[$250] WS - "Rule" tab has unnecessarly long input field for "Days" section

[IuliiaHerets]

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: v9.0.26-1
Reproducible in staging?: Y
Reproducible in production?: Can't check
Email or phone of affected tester (no customers): applausetester+en@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Access staging.new.expensify.com
2. Sign into a valid account
3. Go to Workspace > Workflow > Enable rules
4. Go to "Max Expense Age'" and input a very high number (Note that this field is for Flagging spend older than a specific number of days.)

Expected Result:

User expects that there is a limit of days that can be input and that this limit is reasonable

Actual Result:

User can input absurdly large number of days, numbers that are highly unrealistic for a field like this

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6586795_1724948360909.Absurd_number_of_days.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0183e993ca7b36650e
• Upwork Job ID: 1831043219902619216
• Last Price Increase: 2024-09-03
• Automatic offers:
• ishpaul777 | Reviewer | 103822043
• Nodebrute | Contributor | 103822045

Issue Owner

Current Issue Owner: @ishpaul777

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[IuliiaHerets]

We think that this bug might be related to #wave-collect - Release 1

[puneetlath]

Demoting since rules are in beta