[Due for payment 2025-07-15] [$250] Reports - To field shows red dot next to workspace in confirmation page

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

Action Performed:

1. Launch app
2. Open a workspace chat
3. Create a report
4. Go to self DM
5. Create a track expense without merchant & category
6. Tap report - select the report ID
7. Note the expense is without merchant & category
8. Navigate to workspace chat page
9. Tap plus icon - create expense
10. Enter an amount and tap next
11. Note To field in confirmation page

Expected Result:

To field must not show red dot next to workspace in confirmation page in case tracked expense without merchant and category is moved to workspace

Actual Result:

To field shows red dot next to workspace in confirmation page in case tracked expense without merchant and category is moved to workspace

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6857187_1749661441390.Screenrecorder-2025-06-11-22-24-31-290.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021933569247544867158
• Upwork Job ID: 1933569247544867158
• Last Price Increase: 2025-06-13

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot]

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

[FitseTLT]

I think this is expected. As merchant is required for expense reports the error shows.

[bernhardoj]

Proposal

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

There is a RBR on the To field.

What is the root cause of that problem?

The report has an error on the action, so the RBR shows just like in the LHN. It's from the createOption where it returns the brickRoadIndicator as error.

App/src/libs/OptionsListUtils.ts

Lines 1001 to 1008 in 82a0870

	function getReportOption(participant: Participant): OptionData {
	const report = getReportOrDraftReport(participant.reportID);
	const visibleParticipantAccountIDs = getParticipantsAccountIDsForDisplay(report, true);
	const option = createOption(visibleParticipantAccountIDs, allPersonalDetails ?? {}, !isEmptyObject(report) ? report : undefined, {
	showChatPreviewLine: false,
	forcePolicyNamePreview: false,
	});

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

getReportOption is being used in some IOU flow pages and 1 submit details page (share feature).

If we don't want the RBR to show, we can set the rbr to null.

option.brickRoadIndicator = null;

(we can do it conditionally by passing a new props to getReportOption if needed)

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

N/A

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[ishpaul777]

I think this is expected. As merchant is required for expense reports the error shows.

i beleive there is no need for RBR in the flow becuase we cant take a action on it here

@bernhardoj proposal sounds good adding a prop to conditionally remove it make sense. lets check and fix all other places as well

🎀 👀 🎀