Skip to content

[Due for payment 2025-03-05] [Due for payment 2025-03-05] Reports - Not here page opens when opening system message from #admins #57343

Closed

Description

@vincdargento

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.5-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: N/A
Email or phone of affected tester (no customers): applausetester+sj9032@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Search

Action Performed:

Bug 1:

  1. Go to staging.new.expensify.com
  2. Create a new workspace.
  3. Go to workspace settings > More features.
  4. Enable Invoices.
  5. Go to FAB > Send invoice.
  6. Enter amount > Next.
  7. Select a user.
  8. Submit the invoice.
  9. Go to Reports > Chats.
  10. Refresh the page if system message for member invitation to invoice chat does not appear.
  11. Tap on the system message for member invitation to invoice chat in #admins room.

Bug 2:

  1. Go to staging.new.expensify.com
  2. Create a new workspace.
  3. Delete the workspace.
  4. Go to Reports > Chats.
  5. Tap on the system message "closed the report" in #admins room.

Expected Result:

The correct report will open.

Actual Result:

Not here page opens.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4
bug2.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @strepanier03

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Feb 24, 2025
  2. melvin-bot commented on Feb 24, 2025

    @melvin-bot

    Triggered auto assignment to @strepanier03 (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 Feb 24, 2025

    @melvin-bot

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

  4. melvin-bot commented on Feb 24, 2025

    @melvin-bot

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

  5. github-actions commented on Feb 24, 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. vincdargento commented on Feb 24, 2025

    @vincdargento
    Author

    @strepanier03 FYI 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.

  7. luacmartins commented on Feb 24, 2025

    @luacmartins
    Contributor

    @wildan-m this comes from #54228

  8. luacmartins commented on Feb 25, 2025

    @luacmartins
    Contributor

    Being fixed by this revert

  9. 6 remaining items

  10. melvin-bot commented on Feb 25, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  11. luacmartins commented on Feb 25, 2025

    @luacmartins
    Contributor

    Revert PR CPed. Closing.

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 26, 2025
  13. changed the title [-]Reports - Not here page opens when opening system message from #admins[/-] [+][Due for payment 2025-03-05] Reports - Not here page opens when opening system message from #admins[/+] on Feb 26, 2025
  14. melvin-bot commented on Feb 26, 2025

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2025-03-05. 🎊

  15. melvin-bot commented on Feb 26, 2025

    @melvin-bot

    @luacmartins @strepanier03 @luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  16. changed the title [-][Due for payment 2025-03-05] Reports - Not here page opens when opening system message from #admins[/-] [+][Due for payment 2025-03-05] [Due for payment 2025-03-05] Reports - Not here page opens when opening system message from #admins[/+] on Feb 26, 2025
  17. melvin-bot commented on Feb 26, 2025

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2025-03-05. 🎊

  18. melvin-bot commented on Feb 26, 2025

    @melvin-bot

    @luacmartins @strepanier03 @luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions