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
[Due for payment 2026-01-16] [Due for payment 2026-01-15] Report - Violation for required attendee, disappears after opening "Attendee" field. #79013
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.
Open the Expensify app.
Open any workspace chat.
Start a manual expense creation flow.
Select a category with "Required Attendee" enabled.
Try to submit expense without adding an extra attendee.
Note that a "Required attendee" violation appears.
Open "Attendee" field and return without adding a new attendee.
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.
👋 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.
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
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:
@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]
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
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:
@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]
Activity
melvin-bot commentedon Jan 7, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78315
melvin-bot commentedon Jan 7, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 7, 2026
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.github-actions commentedon Jan 7, 2026
👋 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:
IuliiaHerets commentedon Jan 7, 2026
Chrome / 9.2.95-2
No Required attendees field
Screen.Recording.2026-01-07.at.19.53.35.mp4
6 remaining items
[-]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.[/+]melvin-bot commentedon Jan 8, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 8, 2026
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:
melvin-bot commentedon Jan 8, 2026
@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]
[-][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.[/+]melvin-bot commentedon Jan 9, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 9, 2026
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:
melvin-bot commentedon Jan 9, 2026
@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]