Skip to content

[$250] Expense - Missing Create expense options when opening + menu in 1:1 DM as recipient #71635

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.2.21-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1101/folder/13177029/41237793/927167332
Email or phone of affected tester (no customers): jsndoijsonijsonijs2f@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • User A and User B have not chatted with each other before.
  1. Go to staging.new.expensify.com
  2. [User A] Open FAB > Create expense > Manual.
  3. [User A] Send a manual expense to User B.
  4. [User B] Open 1:1 DM with User A from LHN. Do not open expense report.
  5. [User B] Click + menu.

Expected Result:

Create expense options will be shown.

Actual Result:

Create expense options are missing.

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

Bug6961180_1759283776555.Screen_Recording_2025-10-01_at_09.53.39.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021973493360668250929
  • Upwork Job ID: 1973493360668250929
  • Last Price Increase: 2025-10-01
  • Automatic offers:
    • nkdengineer | Contributor | 108985828
Issue OwnerCurrent Issue Owner: @kadiealexander

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 Oct 1, 2025
  2. melvin-bot commented on Oct 1, 2025

    @melvin-bot

    Triggered auto assignment to @kadiealexander (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 Oct 1, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 1, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 1, 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. Julesssss commented on Oct 1, 2025

    @Julesssss
    Contributor

    @neil-marcellini any progress here?

  7. neil-marcellini commented on Oct 1, 2025

    @neil-marcellini
    Contributor

    Weird, I was not able to reproduce on dev just now, but i was able to reproduce on staging. I'm starting to suspect it is a backend issue. I can verify that by testing on staging Web-E locally. I can't reproduce with that either 😕

  8. 33 remaining items

  9. changed the title [-][Due for payment 2025-10-09] [$250] Expense - Missing Create expense options when opening + menu in 1:1 DM as recipient[/-] [+] [$250] Expense - Missing Create expense options when opening + menu in 1:1 DM as recipient[/+] on Oct 14, 2025
  10. neil-marcellini commented on Oct 29, 2025

    @neil-marcellini
    Contributor

    I believe this is done because it was a regression that @nkdengineer fixed properly after my initial fix, but we can re-open if payment is needed.

  11. nkdengineer commented on Oct 29, 2025

    @nkdengineer
    Contributor

    @neil-marcellini I think the payment is needed here since it's not my regression.

  12. kadiealexander commented on Oct 29, 2025

    @kadiealexander
    Contributor

    Payment Summary

    @rojiphil could you please complete the checklist?

  13. rojiphil commented on Nov 7, 2025

    @rojiphil
    Contributor

    BugZero Checklist:

    • [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

    • [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: Not Required. The existing checklist is good enough to capture such issues.

    • [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.

    Regression Test Proposal Template

    Regression Test Proposal

    Precondition:

    User A and User B have not chatted with each other before.

    Test:

    1. Go to staging.new.expensify.com
    2. [User A] Open FAB > Create expense > Manual.
    3. [User A] Send a manual expense to User B.
    4. [User B] Open 1:1 DM with User A from LHN. Do not open expense report.
    5. [User B] Click + menu.
    6. Verify that: Create expense options will be shown

    Do we agree 👍 or 👎

  14. rojiphil commented on Nov 7, 2025

    @rojiphil
    Contributor

    could you please complete the checklist?

    @kadiealexander BZ Checklist done. Thanks

  15. trjExpensify commented on Nov 10, 2025

    @trjExpensify
    Contributor

    approved $250 for @rojiphil.

  16. JmillsExpensify commented on Dec 1, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @nkdengineer

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions