Skip to content

[Due for payment 2025-04-08] [Report Creation UI] Create report - There are two expense previews after creating a new report #58426

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.13-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): applausetester+ps309@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • User has at least one workspace
  1. Go to staging.new.expensify.com
  2. Go to FAB > Create report.
  3. Go back to Inbox.
  4. Open the workspace chat.

Expected Result:

There will be only one expense preview.

Actual Result:

There are two expense previews after creating a new report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

View all open jobs on GitHubIf 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.13-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): applausetester+ps309@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • User has at least one workspace
  1. Go to staging.new.expensify.com
  2. Go to FAB > Create report.
  3. Go back to Inbox.
  4. Open the workspace chat.

Expected Result:

There will be only one expense preview.

Actual Result:

There are two expense previews after creating a new report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6770213_1741918795209.20250314_101809.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @jliexpensify

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Mar 14, 2025

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

  4. melvin-bot commented on Mar 14, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 14, 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. jliexpensify commented on Mar 14, 2025

    @jliexpensify
    Contributor

    Hmm, how do you create a Report? I'm on Staging v1.13-0 but don't see that option cc @techievivek

  7. jliexpensify commented on Mar 14, 2025

    @jliexpensify
    Contributor

    But I don't think this is a deploy blocker.

  8. 35 remaining items

  9. sumo-slonik commented on Mar 31, 2025

    @sumo-slonik
    Contributor

    It seems to me that this should already be fixed.

  10. added
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Mar 31, 2025
  11. jliexpensify commented on Mar 31, 2025

    @jliexpensify
    Contributor

    Since this is behind a beta, I've asked QA to re-test

  12. kavimuru commented on Mar 31, 2025

    @kavimuru

    Unable to reproduce.

    58795.web.mp4
  13. mountiny commented on Mar 31, 2025

    @mountiny
    Contributor

    Perfect, going to close then thanks

  14. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Mar 31, 2025
  15. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 1, 2025
  16. changed the title [-][Report Creation UI] Create report - There are two expense previews after creating a new report[/-] [+][Due for payment 2025-04-08] [Report Creation UI] Create report - There are two expense previews after creating a new report[/+] on Apr 1, 2025
  17. melvin-bot commented on Apr 1, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  18. melvin-bot commented on Apr 1, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.21-3 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-04-08. 🎊

    For reference, here are some details about the assignees on this issue:

  19. melvin-bot commented on Apr 1, 2025

    @melvin-bot

    @luacmartins / @mountiny @jliexpensify @sumo-slonik / @SzymczakJ 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.EngineeringWeeklyKSv2retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions