Skip to content

[Due for payment 2026-01-16] [Due for payment 2026-01-15] Report - Violation for required attendee, disappears after opening "Attendee" field. #79013

Closed

Description

@jponikarchuk

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): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 / Chrome (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Workspace is on "Control" policy.
Prerequisite 2: "Rules" and "Attendee tracking" enabled.
Prerequisite 3: "Required attendee" for selected category is enabled.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Start a manual expense creation flow.
  4. Select a category with "Required Attendee" enabled.
  5. Try to submit expense without adding an extra attendee.
  6. Note that a "Required attendee" violation appears.
  7. Open "Attendee" field and return without adding a new attendee.
  8. Note that violation disappears.

Expected Result:

Violation for required attendee, should remain visible when returning from "Attendee" field, if no new attendee was added.

Actual Result:

Violation for required attendee, disappears after opening attendee field and returning to report without adding a new attendee.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @stephanieelliott

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    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 @stephanieelliott (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. IuliiaHerets commented on Jan 7, 2026

    @IuliiaHerets

    Chrome / 9.2.95-2
    No Required attendees field

    Screen.Recording.2026-01-07.at.19.53.35.mp4
  7. 6 remaining items

  8. changed the title [-]Report - Violation for required attendee, disappears after opening "Attendee" field.[/-] [+][Due for payment 2026-01-15] Report - Violation for required attendee, disappears after opening "Attendee" field.[/+] on Jan 8, 2026
  9. melvin-bot commented on Jan 8, 2026

    @melvin-bot

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

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

    @melvin-bot

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

  12. changed the title [-][Due for payment 2026-01-15] Report - Violation for required attendee, disappears after opening "Attendee" field.[/-] [+][Due for payment 2026-01-16] [Due for payment 2026-01-15] Report - Violation for required attendee, disappears after opening "Attendee" field.[/+] on Jan 9, 2026
  13. melvin-bot commented on Jan 9, 2026

    @melvin-bot

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

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

    @melvin-bot

    @ikevin127 @stephanieelliott 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