Skip to content

[WAITING ON DOMINICTB][HOLD for payment 2024-08-01] [$250] Report field - List field shows "dropdown" as selected when different initial value is default #44843

Closed

Description

@kavimuru

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.4-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: https://expensify.testrail.io/index.php?/tests/view/4695978
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses.
  4. Go to workspace settings > Report fields.
  5. Click Add field.
  6. Create a List type report field, add a few list values and select an initial value (important).
  7. Go to workspace chat.

Expected Result:

The List type report field will have the initial list value in Step 6 as selected.

Actual Result:

The List type report field shows "dropdown" as the initial list 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

Bug6533100_1720103746001.20240704_223441.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0162c3c8677de552d3
  • Upwork Job ID: 1808914763702199073
  • Last Price Increase: 2024-07-04
  • Automatic offers:
    • shubham1206agra | Contributor | 102994079
Issue OwnerCurrent Issue Owner: @jliexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 4, 2024
  2. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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 Jul 4, 2024

    @melvin-bot

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

  4. github-actions commented on Jul 4, 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.
  5. kavimuru commented on Jul 4, 2024

    @kavimuru
    Author

    @stitesExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  6. kavimuru commented on Jul 4, 2024

    @kavimuru
    Author

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

  7. dominictb commented on Jul 4, 2024

    @dominictb
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    The List type report field shows "dropdown" as the initial list value.

    What is the root cause of that problem?

    we already have the logic to merge the reportField from policy and report in

    const mergedFieldIds = Array.from(new Set([...policyReportFields.map(({fieldID}) => fieldID), ...reportFields.map(({fieldID}) => fieldID)]));

    But we're not setting the optimistic data for report.fieldList in

    so the reportFiled in this case will be the reportField from policy

    const fieldValue = isTitleField ? report.reportName : reportField.value ?? reportField.defaultValue;

    and it has value: dropdown

    What changes do you think we should make in order to solve the problem?

    We can get the report by policyID and expense type.

    then set the optimistic data for reportField of report same as what BE return (without value key)

    Screenshot 2024-07-04 at 23 40 25

    We can check the bug for other field type (text, date) as well.

    What alternative solutions did you explore? (Optional)

    We can remove the value: dropdown in reportField of policy optimistically

    Result

    Screenshot 2024-07-05 at 00 10 07
  8. 46 remaining items

  9. jliexpensify commented on Aug 1, 2024

    @jliexpensify
    Contributor

    bump @dominictb what's your Upworks profile? Could you also add your Upworks name to your GH profile please?

    Alternatively, you can apply here: https://www.upwork.com/jobs/~0162c3c8677de552d3

  10. melvin-bot commented on Aug 1, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@jliexpensify)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1808914763702199073/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. jliexpensify commented on Aug 2, 2024

    @jliexpensify
    Contributor

    Bump @dominictb to provide me with your upworks profile

    Bump @rushatgabhane for checklist

  12. rushatgabhane commented on Aug 2, 2024

    @rushatgabhane
    Member

    @jliexpensify regression steps to add -

    1. Go to workspace settings > Report fields.
    2. Click Add field.
    3. Create a List type report field, add a few list values and select an initial value (important).
    4. Go to workspace chat.
    5. Submit two expenses.
    6. Verify that: The List type report field will have the initial list value as selected
  13. rushatgabhane commented on Aug 2, 2024

    @rushatgabhane
    Member

    no separate payment required for report fields

  14. changed the title [-][HOLD for payment 2024-08-01] [$250] Report field - List field shows "dropdown" as selected when different initial value is default[/-] [+][WAITING ON DOMINICTB][HOLD for payment 2024-08-01] [$250] Report field - List field shows "dropdown" as selected when different initial value is default[/+] on Aug 2, 2024
  15. dominictb commented on Aug 2, 2024

    @dominictb
    Contributor

    @jliexpensify Sorry for the delay, here's my Upwork profile https://www.upwork.com/freelancers/~01f70bed1934fd35d5

  16. jliexpensify commented on Aug 2, 2024

    @jliexpensify
    Contributor

    Thanks @dominictb , invited you.

  17. dominictb commented on Aug 2, 2024

    @dominictb
    Contributor

    @jliexpensify I accepted it thanks 🙏

  18. jliexpensify commented on Aug 2, 2024

    @jliexpensify
    Contributor

    Paid, and job closed.

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions