[$250] Expense preview - Disabled list report field value is displayed on expense preview

[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: v9.1.21-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #57923
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: MacOS Chrome, Desktop
App Component: Money Requests

Action Performed:

1. Enable report fields
2. Go to Report fields > Add field > Add name > select list type > Add list values > select initial value
3. Go offline > Click Save
4. Go to the workspace chat
5. Create expense
6. Return to the workspace Report field
7. Select the list report field > List values > disable all added values
8. Return to the workspace chat > open the expense
9. Apply online mode

Expected Result:

Report field on the expense preview shouldn't be displayed

Actual Result:

Report field on the expense preview shows the report fields initial value

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6784750_1743110346795.Dvnb8264_1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021906953766885392501
• Upwork Job ID: 1906953766885392501
• Last Price Increase: 2025-05-06

Issue Owner

Current Issue Owner: @Pujan92

[melvin-bot]

Triggered auto assignment to @kadiealexander (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.

[nkdengineer]

Proposal

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

Report field on the expense preview shows the report fields initial value

What is the root cause of that problem?

We only hide the report field if the fieldValue is not empty. In our case reportField.defaultValue is not empty then this returns false.

App/src/components/ReportActionItem/MoneyReportView.tsx

Lines 100 to 104 in 045a3ba

	const shouldHideSingleReportField = (reportField: PolicyReportField) => {
	const fieldValue = reportField.value ?? reportField.defaultValue;
	const hasEnableOption = reportField.type !== CONST.REPORT_FIELD_TYPES.LIST || reportField.disabledOptions.some((option) => !option);
	return isReportFieldOfTypeTitle(reportField) || (!fieldValue && !hasEnableOption);

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

I think we can remove !fieldValue check here

App/src/components/ReportActionItem/MoneyReportView.tsx

Lines 100 to 104 in 045a3ba

	const shouldHideSingleReportField = (reportField: PolicyReportField) => {
	const fieldValue = reportField.value ?? reportField.defaultValue;
	const hasEnableOption = reportField.type !== CONST.REPORT_FIELD_TYPES.LIST || reportField.disabledOptions.some((option) => !option);
	return isReportFieldOfTypeTitle(reportField) || (!fieldValue && !hasEnableOption);

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

UI bug.

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[github-actions]

⚠️ @nkdengineer Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

[FitseTLT]

Proposal

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

Expense preview - Disabled list report field value is displayed on expense preview

What is the root cause of that problem?

We won't hide the field if we the list report field has a defaultValue

App/src/components/ReportActionItem/MoneyReportView.tsx

Lines 100 to 104 in 045a3ba

	const shouldHideSingleReportField = (reportField: PolicyReportField) => {
	const fieldValue = reportField.value ?? reportField.defaultValue;
	const hasEnableOption = reportField.type !== CONST.REPORT_FIELD_TYPES.LIST || reportField.disabledOptions.some((option) => !option);
	return isReportFieldOfTypeTitle(reportField) || (!fieldValue && !hasEnableOption);

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

We need to only avoid hiding the field only if it has a previously set value (defaultValue shouldn't matter) so we should remove the reportField.defaultValue from here

App/src/components/ReportActionItem/MoneyReportView.tsx

Line 101 in 045a3ba

const fieldValue = reportField.value ?? reportField.defaultValue;

This is exactly the logic we use for other list fields like category in other places as here

App/src/components/ReportActionItem/MoneyRequestView.tsx

Line 218 in 1c74508

const shouldShowCategory = isPolicyExpenseChat && (transactionCategory || hasEnabledOptions(policyCategories ?? {}));

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

Not needed

What alternative solutions did you explore? (Optional)

[melvin-bot]

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

[melvin-bot]

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