[Due for payment 2026-06-30] [Due for payment 2026-06-18] [Due for payment 2026-06-17] Report fields - Initial value error persists after selecting an initial value

[applause-bot]

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.4.2-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91627
Email or phone of affected tester (no customers): sjdoisjndojsdoijsioj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com
   2 Go to workspace settings > Reports.
2. Enable Report fields and upgrade workspace if needed.
3. Click Add field.
4. Click Name, enter name and save it.
5. Click Type and select List.
6. Click List values and add a list value.
7. Click RHP back button.
8. Click Save.
9. Click Initial value.
10. Select an initial value.

Expected Result:

Initial value error will dismiss after selecting an initial value.

Actual Result:

Initial value error persists after selecting an initial value.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7176883_1781101263793.9.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7176883

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/3b115f0bfaeb7307ea83a7361f588ea2e26e8eeaf60e11d146f030fb3d77af6f

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91627

[melvin-bot]

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

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

[mountiny]

@MelvinBot Can you do a clean revert of #93153 and then #91627 prs?