-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[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
Comments
Triggered auto assignment to @jliexpensify ( |
Triggered auto assignment to @stitesExpensify ( |
👋 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:
|
@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. |
We think this bug might be related to #wave-collect - Release 1 |
ProposalPlease 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 Line 2580 in f73cdc4
But we're not setting the optimistic data for report.fieldList in App/src/libs/actions/Policy/ReportFields.ts Line 154 in f73cdc4
so the reportFiled in this case will be the reportField from policy
and it has 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 We can check the bug for other field type (text, date) as well. What alternative solutions did you explore? (Optional)We can remove the Result |
Updated proposal to add the result |
@dominictb can you please create a PR for this? Were you able to identify if this is a regression, and if so, from which PR? |
Job added to Upwork: https://www.upwork.com/jobs/~0162c3c8677de552d3 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
Report fields are under a beta and this doesn't really break anything, so removing the deployer label. |
Approved, pending internal review and merge |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.11-5 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 2024-08-01. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@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 |
Payment Summary
|
@rushatgabhane will be given payment at the end of project. |
Cheers, fixed! |
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 |
Payment Summary
BugZero Checklist (@jliexpensify)
|
Bump @dominictb to provide me with your upworks profile Bump @rushatgabhane for checklist |
@jliexpensify regression steps to add -
|
no separate payment required for report fields |
@jliexpensify Sorry for the delay, here's my Upwork profile https://www.upwork.com/freelancers/~01f70bed1934fd35d5 |
Thanks @dominictb , invited you. |
@jliexpensify I accepted it thanks 🙏 |
Paid, and job closed. |
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:
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?
Screenshots/Videos
Bug6533100_1720103746001.20240704_223441.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: