Skip to content

[Due for payment 2025-09-19] [Due for payment 2025-09-17] Report field shows an error that it is required when the initial value is set #70171

Closed

Description

@jponikarchuk

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.3-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #66918
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.6.1 Chrome, iPhone 15 iOS 18.5 Safari
App Component: Other

Action Performed:

  1. Sign in to ND
  2. Create a workspace, enable report fields for the workspace.
  3. Create a text report field with a name, enter initial value and save
  4. Create an expense in the workspace chat
  5. Open the expense details, observe the report field

Expected Result:

The error is not shown in the report field since it is filled with the initial value

Actual Result:

The error is shown in the report field, that it is required, even though it is filled with the initial value

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 9, 2025
  2. melvin-bot commented on Sep 9, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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 Sep 9, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 9, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 9, 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. rlinoz commented on Sep 9, 2025

    @rlinoz
    Contributor

    Draft with the fix is here #70188

    cc: @Tony-MK @rushatgabhane

  7. m-natarajan commented on Sep 9, 2025

    @m-natarajan

    Not reproducible on Win 11/Chrome and iPhone 16/18.3.1 build v9.2.3-2

    ScreenRecording_09-09-2025.10-37-03_1.MP4
    Recording.280.mp4
  8. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 9, 2025
  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 10, 2025
  10. changed the title [-]Report field shows an error that it is required when the initial value is set[/-] [+][Due for payment 2025-09-17] Report field shows an error that it is required when the initial value is set[/+] on Sep 10, 2025
  11. melvin-bot commented on Sep 10, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Sep 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.8-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-09-17. 🎊

  13. melvin-bot commented on Sep 10, 2025

    @melvin-bot

    @rlinoz @JmillsExpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. changed the title [-][Due for payment 2025-09-17] Report field shows an error that it is required when the initial value is set[/-] [+][Due for payment 2025-09-19] [Due for payment 2025-09-17] Report field shows an error that it is required when the initial value is set[/+] on Sep 12, 2025
  15. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-09-19. 🎊

  16. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    @rlinoz @JmillsExpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions