Expense - Missing dot separator between Attendees and "x per person" in transaction thread

[mitarachim]

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.40-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: #60067
Email or phone of affected tester (no customers): applausetester+300402kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Scan
4. Upload a receipt.
5. On confirmation page, click Show more.
6. Click Attendees.
7. Select one more attendee.
8. Click Save.
9. Click Create expense.
10. Go to transaction thread.
11. Wait for the scan to complete.

Expected Result:

There will be a dot separator between Attendees and "x per person" in transaction thread.

Actual Result:

Dot separator is missing between Attendees and "x per person" in transaction thread.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6822631_1746495526514.20250506_093454.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @allroundexperts

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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.

[ra-md]

Proposal

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

Missing dot separator between Attendees and "x per person" in transaction thread

What is the root cause of that problem?

Missing ${CONST.DOT_SEPARATOR} in the description of the Attendees MenuItemWithTopDescription

App/src/components/ReportActionItem/MoneyRequestView.tsx

Lines 764 to 768 in 0601503

	description={`${translate('iou.attendees')} ${
	Array.isArray(transactionAttendees) && transactionAttendees.length > 1 && formattedPerAttendeeAmount
	? `${formattedPerAttendeeAmount} ${translate('common.perPerson')}`
	: ''
	}`}

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

Add ${CONST.DOT_SEPARATOR} before ${formattedPerAttendeeAmount}

description={`${translate('iou.attendees')} ${
    Array.isArray(transactionAttendees) && transactionAttendees.length > 1 && formattedPerAttendeeAmount
        ? `${CONST.DOT_SEPARATOR} ${formattedPerAttendeeAmount} ${translate('common.perPerson')}`
        : ''
}`}

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

N/A

What alternative solutions did you explore? (Optional)

N/A

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.