Skip to content

[Due for payment 2025-12-23] Expense - Duplicated expense is not created after duplicating IOU expense #77303

Closed

Description

@lanitochka17

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.2.75-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75323
Email or phone of affected tester (no customers): siodjosijdsojsojsodj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Account does not have self DM.
  • Account does not have workspace.
  1. Go to staging.new.expensify.com
  2. Open 1:1 DM.
  3. Create an expense.
  4. Open the expense report.
  5. Click More > Duplicate.

Expected Result:

Duplicated expense will be created in self DM or 1:1 DM

Actual Result:

Duplicated expense is not created when duplicating IOU expense.

*If self DM exists, it will appear in self DM.

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

Bug7026191_1765404306351.7.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

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

    @melvin-bot

    Triggered auto assignment to @NicMendonca (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 Dec 10, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 10, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 10, 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. changed the title [-]77285 Expense - Duplicated expense is not created after duplicating IOU expense[/-] [+] Expense - Duplicated expense is not created after duplicating IOU expense[/+] on Dec 10, 2025
  7. jjcoffee commented on Dec 11, 2025

    @jjcoffee
    Contributor

    @lanitochka17 Do you have a self-DM on that account?

  8. jjcoffee commented on Dec 11, 2025

    @jjcoffee
    Contributor

    I wonder if we should create a self-DM if one doesn't already exist (and there's no default workspace). This seems to be what happens on OD.

  9. 26 remaining items

  10. changed the title [-] Expense - Duplicated expense is not created after duplicating IOU expense[/-] [+][Due for payment 2025-12-23] Expense - Duplicated expense is not created after duplicating IOU expense[/+] on Dec 16, 2025
  11. melvin-bot commented on Dec 16, 2025

    @melvin-bot

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

  12. melvin-bot commented on Dec 16, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.78-8 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-12-23. 🎊

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

    • @jjcoffee requires payment through NewDot Manual Requests
  13. melvin-bot commented on Dec 16, 2025

    @melvin-bot

    @jjcoffee @NicMendonca 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]

  14. melvin-bot commented on Dec 23, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@NicMendonca)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. mallenexpensify commented on Dec 24, 2025

    @mallenexpensify
    Contributor

    Doesn't look like @jjcoffee is due payment here, didn't see review of the linked PR

  16. melvin-bot commented on Dec 27, 2025

    @melvin-bot

    @NicMendonca Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  17. jjcoffee commented on Dec 29, 2025

    @jjcoffee
    Contributor

    Yup, this was a regression, no payment needed!

  18. JS00001 commented on Dec 29, 2025

    @JS00001
    Contributor

    Going to close out since no payment needed

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions