Reports - Report name for thread in workspace chat is workspace name instead of thread title

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.95-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Open 1:1 DM.
3. Send a message.
4. Right click on the message > Reply in thread.
5. Send a reply in thread.
6. Go to Reports > Chats.
7. Note that the report name for thread in 1:1 DM is the thread header title.
8. Go to workspace chat.
9. Send a message.
10. Right click on the message > Reply in thread.
11. Send a reply in thread.
12. Go to Reports > Chats.

Expected Result:

The report name for thread in workspace chat should be the thread header title.

Actual Result:

The report name for thread in workspace chat is the workspace name.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6736021_1738918541239.20250207_165205.mp4

View all open jobs on GitHub

[melvin-bot]

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

[NJ-2020]

I think this the expected

#50135

[luacmartins]

Not a blocker. @JmillsExpensify @trjExpensify can you confirm the expected behavior here? I kinda like having the top level report as the context instead of the thread message. Either way, I don't think this is a blocker.

[trjExpensify]

Yeah, I'm pretty sure that's what we said for the v1 here, because otherwise we need to compute a lot of titles like system messages and stuff wasn't it?

[luacmartins]

Yea, that's what I thought as well. So we can just close this for now?

[trjExpensify]

Yep!