Skip to content

[READY FOR PAYMENT][$125] Report fields - List type report field shows "List is required" when there is an initial value #46223

Closed

Description

@lanitochka17

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.0.12-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #44139

Action Performed:

Precondition:

  • Workspace is under Control plan
  • Report fields feature is enabled
  • List type report field is added, and the list has an initial value
  1. Go to workspace chat
  2. Split a manual expense
  3. Go to Troubleshoot > Clear cache and restart > Reset and restart
  4. Go to workspace chat
  5. Split another manual expense (because violations do not show up instantly)
  6. Go to expense report

Expected Result:

List type report field will not display "List is required" violation because there is an initial value

Actual Result:

List type report field displays "List is required" violation when there is an initial value

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6552686_1721913687120.20240725_212026.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01fa66587c84d7c165
  • Upwork Job ID: 1823770004376025525
  • Last Price Increase: 2024-08-14
  • Automatic offers:
    • nkdengineer | Contributor | 103527627
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 25, 2024
  2. melvin-bot commented on Jul 25, 2024

    @melvin-bot

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

  3. github-actions commented on Jul 25, 2024

    @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.
  4. francoisl commented on Jul 25, 2024

    @francoisl
    Contributor

    @thienlnam is this also something about report fields we can polish with a follow-up PR?

  5. Beamanator commented on Jul 25, 2024

    @Beamanator
    Contributor

    Assigning jack since this is part of your Report Field Violations Project 🙏

  6. Beamanator commented on Jul 25, 2024

    @Beamanator
    Contributor

    Also if this is under beta we can demote, is there a report fields beta? reportFieldsFeature i think?

  7. thienlnam commented on Jul 25, 2024

    @thienlnam
    Contributor

    Yeah, we definitely can address - @jnowakow another one to fix

  8. thienlnam commented on Jul 25, 2024

    @thienlnam
    Contributor

    @Beamanator That beta is for setting up report fields in NewDot - slightly unrelated to showing them, but I don't think this needs to be a blocker

  9. 53 remaining items

  10. melvin-bot commented on Sep 23, 2024

    @melvin-bot

    This issue has not been updated in over 14 days. @JmillsExpensify, @thienlnam, @war-in, @nkdengineer eroding to Weekly issue.

  11. nkdengineer commented on Sep 30, 2024

    @nkdengineer
    Contributor
  12. melvin-bot commented on Oct 16, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @JmillsExpensify, @thienlnam, @war-in, @nkdengineer eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  13. nkdengineer commented on Oct 30, 2024

    @nkdengineer
    Contributor
  14. JmillsExpensify commented on Nov 27, 2024

    @JmillsExpensify
    Contributor

    Ah sorry I missed this in my filters as the payment has no date.

  15. JmillsExpensify commented on Nov 27, 2024

    @JmillsExpensify
    Contributor

    All paid out. Closing this one.

  16. moved this from Hold for Payment to Done in #expensify-bugson Nov 27, 2024
  17. garrettmknight commented on Jun 10, 2025

    @garrettmknight
    Contributor

    Payment summary:

  18. JmillsExpensify commented on Jun 10, 2025

    @JmillsExpensify
    Contributor

    $125 approved for @allroundexperts

  19. allroundexperts commented on Jun 10, 2025

    @allroundexperts
    Contributor

    @garrettmknight @JmillsExpensify My payment is $250 here (which is the standard amount for a deploy blocker PR review). We paid $125 to @nkdengineer because there proposal was used by the SWM team.

  20. allroundexperts commented on Jun 10, 2025

    @allroundexperts
    Contributor

    Actually, I just checked again and this was a regression issue of a PR that I reviewed. I am not due for any compensation here. I will remove the expense from the report.

  21. JmillsExpensify commented on Jun 10, 2025

    @JmillsExpensify
    Contributor

    Ah thanks!

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions