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
WS - Attendees are not tracked by default on Control workspace #104166
Version Number: v9.5.10-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#103958 Email or phone of affected tester (no customers):applausetester+bm8900011@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Web, android App Component: Workspace Settings
Action Performed:
Preconditions:
Control workspace exists with rules enabled
Go to staging.new.expensify.com
Go to Workspace Settings > Rules
Expected Result:
Attendees fields should be shown by default
Actual Result:
Attendees fields are not shown on expenses by default (Step 6 of test 2 fails)
Root Cause: This is expected behavior, not a bug. A workspace upgraded to Control in New Expensify starts with attendee tracking off on purpose. Only older Control workspaces that have no isAttendeeTrackingEnabled value track attendees by default.
Recommended Fix: No code change. Close this issue. To retest, turn on Workspace > Rules > Attendee tracking first, then check that the Attendees field shows on the confirmation page.
Investigation details
The Attendees field shows only when the workspace is Control and isAttendeeTrackingEnabled(policy) is true: TransactionUtils/index.ts:458-464.
Not verified: the stored value on the tester's workspace. If product now wants upgraded Control workspaces to track attendees by default, that is a new feature request. It would also need a backend change.
Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.
this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
applause-bot commentedon Oct 15, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/792bc36efa1548fc144a5bee0737591ac15b7477d19578ba9d4c376fee9d9028
MelvinBot commentedon Oct 15, 2026
Issue Analysis
Root Cause: This is expected behavior, not a bug. A workspace upgraded to Control in New Expensify starts with attendee tracking off on purpose. Only older Control workspaces that have no
isAttendeeTrackingEnabledvalue track attendees by default.PolicyUtils/features.ts:23-25treats a missing value as on for Control workspaces.Policy.ts:6069sets the value tofalsewhen a workspace upgrades to Control.This was decided in Update default enabled logic for Attendee Tracking feature and built in Consider Attendee Tracking enabled by default for existing Corporate policies (June 2025). The tester's workspace was likely upgraded in New Expensify, so tracking is off.
The bug report comes from QA step 6 of [Refactor] Move PolicyUtils rules, feature, workflow, and error helpers into rules.ts, features.ts, workflows.ts, and errors.ts. That step says "Control workspaces track attendees by default," which is wrong for upgraded workspaces. That PR only moved code; it didn't change this logic. This is why the issue also reproduces in production.
Recommended Fix: No code change. Close this issue. To retest, turn on Workspace > Rules > Attendee tracking first, then check that the Attendees field shows on the confirmation page.
Investigation details
isAttendeeTrackingEnabled(policy)is true:TransactionUtils/index.ts:458-464.IndividualExpenseRulesSectionRevamp.tsx:312-324.false." PR Consider Attendee Tracking enabled by default for existing Corporate policies #63520's QA test checks that the toggle is off after an upgrade.falseset on upgrade.Next Steps: Reply with
@MelvinBot <your feedback>to refine this analysis.view run
melvin-bot commentedon Oct 20, 2026
Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Oct 22, 2026
Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Oct 26, 2026
10 days overdue. Is anyone even seeing these? Hello?
melvin-bot commentedon Oct 28, 2026
12 days overdue now... This issue's end is nigh!
melvin-bot commentedon Oct 29, 2026
this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
melvin-bot commentedon Nov 2, 2026
This issue has not been updated in over 14 days. eroding to Weekly issue.