Skip to content

mWeb - Expense - Renamed the report system message is shown incorrectly. #53820

Description

@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.73-6
Reproducible in staging?: Yes
Reproducible in production?: No
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
Email or phone of affected tester (no customers): N
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to https://staging.new.expensify.com/home
  2. Open a workspace chat
  3. Create a expense
  4. Open the expense

Expected Result:

Renamed the report system message must not be shown.

Actual Result:

Renamed the report system message is shown incorrectly.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6689697_1733811792457.Screenrecorder-2024-12-10-11-46-13-39.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Dec 10, 2024
  2. melvin-bot commented on Dec 10, 2024

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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. IuliiaHerets commented on Dec 10, 2024

    @IuliiaHerets
    Author

    Production

    ScreenRecording_12-10-2024.13-36-20_1.MP4
  4. jliexpensify commented on Dec 10, 2024

    @jliexpensify
    Contributor

    @IuliiaHerets is this an actual Deploy Blocker, or did you accidentally use the label?

  5. jliexpensify commented on Dec 10, 2024

    @jliexpensify
    Contributor

    I can't repro on staging or prod v73-6 (Pixel 7) - closing:

    Screenshot_20241210-204807

  6. IuliiaHerets commented on Dec 10, 2024

    @IuliiaHerets
    Author

    @jliexpensify No, I added the label on purpose. Issue was reproduced in stg and prod with staging server off, issue was not repro with SS on.
    QA team can still repro this issue

    Screenrecorder-2024-12-10-18-49-03-770.mp4
  7. IuliiaHerets commented on Dec 10, 2024

    @IuliiaHerets
    Author

    Production @jliexpensify

    Screenrecorder-2024-12-10-18-57-16-578.mp4
  8. jliexpensify commented on Dec 10, 2024

    @jliexpensify
    Contributor

    Clarifying if this is a true deploy blocker here

  9. 6 remaining items

  10. jliexpensify commented on Dec 10, 2024

    @jliexpensify
    Contributor

    Hi @francoisl - Applause seems to think this is a deploy blocker, but I don't think it is (and I can't repro). Puneet advised applying both labels here.

  11. francoisl commented on Dec 11, 2024

    @francoisl
    Contributor

    I can repro on Web on staging, looking now. Not sure if it's a backend or NewDot blocker yet, let's keep both labels for now.

  12. francoisl commented on Dec 11, 2024

    @francoisl
    Contributor

    This is a backend bug caused by https://github.com/Expensify/Web-Expensify/pull/44662/, removing the NewDot blocker label.

  13. deetergp commented on Dec 11, 2024

    @deetergp
    Contributor

    I think the revert of https://github.com/Expensify/Web-Expensify/pull/44662 worked and we're good to remove the blocker label.

    2024-12-11_10-08-59.mp4
  14. deetergp commented on Dec 11, 2024

    @deetergp
    Contributor
  15. francoisl commented on Dec 11, 2024

    @francoisl
    Contributor

    We cherry-picked a backend fix https://github.com/Expensify/Web-Expensify/pull/44733. Both Scott and I confirmed the regression is no longer on staging, removing the blocker label.

  16. mvtglobally commented on Dec 12, 2024

    @mvtglobally
  17. jliexpensify commented on Dec 12, 2024

    @jliexpensify
    Contributor

    Awesome, are we good to close this @francoisl @deetergp ?

  18. deetergp commented on Dec 13, 2024

    @deetergp
    Contributor

    Looks that way @jliexpensify. Closing!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions