[$500] [MEDIUM] IOU - Report fields are blank after refresh or leave from report

[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: 1.4.36-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): applausetester+01022024_emp@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Issue found when executing PR #34483

Action Performed:

1. In Old dot, create a new Collect / Control policy
2. Go to the settings of this workspace and execute the following in console:
   p = Policy.getCurrent();
   p.policy.isPolicyExpenseChatEnabled = "true";
   p.save();
3. Go to the reports section of the settings of the newly create workspace and add some report fields
4. Invite a user to be a member of this new workspace
5. In NewDot, login as the invited user. Make sure canUseReportFields beta is enabled for the user
6. Go to the workspace chat room and request some money
7. Open the created expense report
8. Verify that the custom fields show up
9. Click on each of the field
10. Enter a value and save it

Expected Result:

Make sure that the field gets saved successfully and you can submit report

Actual Result:

When leaving and re-entering the report the fields have been cleared, it also happens after refreshing
Report present error after you try to submit

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

Bug6366369_1707000347908.PR_34483_Web.mp4

Bug6366369_1707000347888.PR_34483_Mweb.mp4

Bug6366369_1707000347888.PR_34483_Mweb.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~017fe95e1509261ee2
• Upwork Job ID: 1754149879851364352
• Last Price Increase: 2024-02-11

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~017fe95e1509261ee2

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[stephanieelliott]

Repro steps are clear and this seems like something that should be fixed. Let's wait for some proposals.

[HezekielT]

I think this is a backend issue. The OpenReport api call is returning null for the report field's value which is why the fields are cleared.

[getusha]

Thanks @HezekielT
@stephanieelliott could we get internal engineer on this?

[stephanieelliott]

I think this should be tackled as part of Wave 6, posted to get confirmation here as a first step to try and source an internal engineer.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@stephanieelliott, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick!

[getusha]

backend issue

[melvin-bot]

Current assignee @getusha is eligible for the Internal assigner, not assigning anyone new.

[stephanieelliott]

Hey @thienlnam I noticed you are working on a bunch of issues related to report fields -- any chance you have the bandwidth to grab this one too?

[thienlnam]

Yeah, I thought this was solved but I can take another look

[stephanieelliott]

Fix for this is on staging

[stephanieelliott]

Solved internally, no C+ review on this one so no payment due