[$250] Reports - Multi tags are separated by colon instead of comma

[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.3.11-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80638
Email or phone of affected tester (no customers): sjdiojnsodjsosjio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Workspace has multi level tags.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense with multi tags.
4. Go to Reports > Expenses.
5. Click Filters > Group by.
6. Select Tag > click Save.
7. Click View results.

Expected Result:

Multi tags will be separated by comma.

Actual Result:

Multi tags are separated by colon.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7060737_1769644235493.4.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022016991584354557228
• Upwork Job ID: 2016991584354557228
• Last Price Increase: 2026-01-29
• Automatic offers:
• aimane-chnaif | Reviewer | 110294735

Issue Owner

Current Issue Owner: @

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #80638

[melvin-bot]

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

[melvin-bot]

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

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