You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Expense - Missing Create expense options when opening + menu in 1:1 DM as recipient #71635
👋 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:
Identify the pull request that introduced this issue and revert it.
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 😕
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
[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
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Oct 1, 2025
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.melvin-bot commentedon Oct 1, 2025
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 1, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 1, 2025
👋 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:
Julesssss commentedon Oct 1, 2025
@neil-marcellini any progress here?
neil-marcellini commentedon Oct 1, 2025
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 😕
33 remaining items
[-][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[/+]neil-marcellini commentedon Oct 29, 2025
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.
nkdengineer commentedon Oct 29, 2025
@neil-marcellini I think the payment is needed here since it's not my regression.
kadiealexander commentedon Oct 29, 2025
Payment Summary
@rojiphil could you please complete the checklist?
rojiphil commentedon Nov 7, 2025
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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/566433
Regression Test Proposal
Precondition:
User A and User B have not chatted with each other before.
Test:
Do we agree 👍 or 👎
rojiphil commentedon Nov 7, 2025
@kadiealexander BZ Checklist done. Thanks
trjExpensify commentedon Nov 10, 2025
approved $250 for @rojiphil.
JmillsExpensify commentedon Dec 1, 2025
$250 approved for @nkdengineer