Skip to content

[$250] Reports - Chat bubble only appears on expense preview after opening the report #62529

Closed

Description

@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.48-0
Reproducible in staging?: Yes
Reproducible in production?: No
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): applausetester+160510kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android 14
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit an expense.
  4. Go to Reports.
  5. Tap bookmark icon.
  6. Tap Expense Reports.
  7. Long press on the expense from Step 3.
  8. Tap Select.
  9. Tap dropdown button > Hold.
  10. Enter reason and save it.
  11. Exit selection mode by tapping app back button.
  12. Note that there is no chat bubble on the expense preview.
  13. Tap on the expense.
  14. Tap app back button.
  15. Now chat bubble appeears on the expense preview after opening the report.

Expected Result:

In Step 12, after holding expense from Reports, chat bubble will appear on the expense preview.

Actual Result:

In Step 12, after holding expense from Reports, chat bubble does not appear on the expense preview.
It only appears after opening the report in Step 15.

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

Bug6838572_1747855746676.Screen_Recording_20250522_032524_Chrome.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021933332163910513232
  • Upwork Job ID: 1933332163910513232
  • Last Price Increase: 2025-06-13
  • Automatic offers:
    • allgandalf | Reviewer | 107727638
    • truph01 | Contributor | 107727640
Issue OwnerCurrent Issue Owner: @twisterdotcom

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on May 21, 2025
  2. melvin-bot commented on May 21, 2025

    @melvin-bot

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

  3. melvin-bot commented on May 21, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 21, 2025

    @melvin-bot

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

  5. github-actions commented on May 21, 2025

    @github-actions
    Contributor

    👋 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.
  6. aldo-expensify commented on May 22, 2025

    @aldo-expensify
    Contributor

    Trying to reproduce...

  7. aldo-expensify commented on May 22, 2025

    @aldo-expensify
    Contributor

    The threadMessages.count is 0 before opening the report and 1 after opening:

  8. 70 remaining items

  9. allgandalf commented on Jun 25, 2025

    @allgandalf
    Contributor

    Hopeful to get the PR merged this week

  10. melvin-bot commented on Jul 18, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @twisterdotcom, @sonialiap, @aldo-expensify, @allgandalf, @truph01 eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  11. truph01 commented on Sep 3, 2025

    @truph01
    Contributor

    The PR is deployed to prod for a week. It looks like BOT doesn't work in this case

  12. allgandalf commented on Sep 3, 2025

    @allgandalf
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: N/A Optimistic case was never considered for reports page

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/543579

    Regression Test Proposal

    Precondition:

    Test:

    1. Go to workspace chat.
    2. Submit an expense.
    3. Go to Reports.
    4. Tap bookmark icon.
    5. Tap Expense Reports.
    6. Long press on the expense from Step 3.
    7. Tap Select.
    8. Tap dropdown button > Hold.
    9. Enter reason and save it.
    10. Exit selection mode by tapping app back button.

    Verify: After holding expense from Reports, chat bubble will appear on the expense preview.

    Do we agree 👍 or 👎

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Sep 3, 2025
  14. twisterdotcom commented on Sep 3, 2025

    @twisterdotcom
    Contributor

    Payment Summary:

  15. twisterdotcom commented on Sep 10, 2025

    @twisterdotcom
    Contributor

    @allgandalf when going to add this test, we see that "After holding expense from Reports, chat bubble will appear on the expense preview." doesn't happen.

    Has there been a regression here?

  16. truph01 commented on Sep 10, 2025

    @truph01
    Contributor

    @twisterdotcom The bug you mentioned was already reported here. And based on the RCA, it isn't caused by our PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions