Skip to content

[Due for payment 2026-01-16] [Due for payment 2026-01-15] Expense - No attendee require violation on confirm page when there is no additional attendee #79011

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.95-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: #78315
Email or phone of affected tester (no customers): sdosdijsoidjsiosdjndisoj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Preconditions:

  • Rules are enabled.
  • Enable Attendee tracking in Rules.
  • Make Advertising category require attendees in category settings.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Click + > Create expense > Manual.
  4. Enter amount > Next.
  5. On confirm page, select Advertising category and click Attendees.
  6. Add one more attendee and click Save.
  7. Click Create expense.
  8. Open the expense.
  9. Click Attendees and remove the attendee added in Step 6.
  10. Go back to self DM.
  11. Click Submit it to someone.
  12. Select the workspace chat.
  13. Enter merchant.
  14. Without selecting additional attendee, click Create expense.

Expected Result:

App should show attendee require violation on confirm page when there is no additional attendee.

Actual Result:

App does not show attendee require violation on confirm page when there is no additional attendee.

This issue only happens when Step 9 is performed.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Bug7042867_1767796379507.4.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

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 Jan 7, 2026
  2. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78315

  3. melvin-bot commented on Jan 7, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    Triggered auto assignment to @sonialiap (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.

  5. github-actions commented on Jan 7, 2026

    @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. 8 remaining items

  7. changed the title [-]Expense - No attendee require violation on confirm page when there is no additional attendee[/-] [+][Due for payment 2026-01-15] Expense - No attendee require violation on confirm page when there is no additional attendee[/+] on Jan 8, 2026
  8. melvin-bot commented on Jan 8, 2026

    @melvin-bot

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

  9. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.95-5 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 2026-01-15. 🎊

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

    • @ikevin127 requires payment through NewDot Manual Requests
  10. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    @ikevin127 @sonialiap 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]

  11. changed the title [-][Due for payment 2026-01-15] Expense - No attendee require violation on confirm page when there is no additional attendee[/-] [+][Due for payment 2026-01-16] [Due for payment 2026-01-15] Expense - No attendee require violation on confirm page when there is no additional attendee[/+] on Jan 9, 2026
  12. melvin-bot commented on Jan 9, 2026

    @melvin-bot

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

  13. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-6 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 2026-01-16. 🎊

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

    • @ikevin127 requires payment through NewDot Manual Requests
  14. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    @ikevin127 @sonialiap 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.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions