[HOLD for payment 2024-08-22] Search filters - Tag in X: Y format is displayed in X\:Y style

[IuliiaHerets]

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.0.20-4
Reproducible in staging?: Y
Reproducible in production?: N (Can't check)
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• Workspace has a tag in X: Y format.

1. Go to staging.new.expensify.com/search/filters.
2. Click Tag.

Expected Result:

Tag in X: Y format will be displayed in X:Y style.

Actual Result:

Tag in X: Y format is displayed in X\:Y style

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

20240815_002902.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @kadiealexander

[melvin-bot]

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

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

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

[IuliiaHerets]

We think that this bug might be related to #wave-collect - Release 1

[Beamanator]

This one def looks like it's related to #46556 and #47289

[Beamanator]

cc @bernhardoj @getusha

[Beamanator]

Looks fixed in staging! probably can close this out

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.20-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Clean tag name #47451

If no regressions arise, payment will be issued on 2024-08-22. 🎊

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@chiragsalian] The PR that introduced the bug has been identified. Link to the PR: Fix no error when saving same tag name in X:Y format #46556
• [@chiragsalian] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: Fix no error when saving same tag name in X:Y format #46556 (comment)
• [@chiragsalian] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A, the filter screen is new so its a new bug.
• [@chiragsalian] Determine if we should create a regression test for this bug. I think not worth it atm
• [@chiragsalian] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
• [@kadiealexander] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[chiragsalian]

No payment needed here since i solved this internally.