[HOLD for payment 2024-06-06] [$250] [Held requests] Reason appears bolded briefly after holding the request

[izarutskaya]

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: 1.4.63-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Go to staging.new.expensify.com
2. Create a manual request in the workspace chat.
3. Create a second request if there is only one request as Hold request option is not showing in the combined report.
4. Go to transaction thread.
5. Click 3-dot menu > Hold request.
6. Enter a reason and save it.

Expected Result:

The reason in the transaction thread will not appear bolded.

Actual Result:

The reason in the transaction thread is bolded briefly after holding the request.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Bug6453293_1713425278170.hold_request_bold.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~012e7d4583f2b70df4
• Upwork Job ID: 1780902555749208064
• Last Price Increase: 2024-04-18
• Automatic offers:
• GandalfGwaihir | Contributor | 0
• hoangzinh | Contributor | 0

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

Triggered auto assignment to @trjExpensify (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 @techievivek (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[izarutskaya]

@trjExpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[izarutskaya]

We think this issue might be related to the #collect project.

[allgandalf]

@trjExpensify, This issue was reported by me on slack, I also Proposed the fix over there. (this issue is reproducible on production as well)

c.c. @shawnborton @dannymcclain @robertjchen