Reports- Attendees&Per attendee are still enabled by default after disabling Attendee tracking

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

Action Performed:

Precondition:

• Rules are enabled.
• Attendee tracking is enabled in Rules.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Go to workspace settings > Rules.
5. Disable Attendee tracking.
6. Go to Reports > Expenses.
7. Click Columns.

Expected Result:

Attendees and Per attendee should not be enabled by default after disabling Attendee tracking because both columns are also hidden from the expense table.

Actual Result:

Attendees and Per attendee are still enabled by default after disabling Attendee tracking.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7120179_1775161461128.8.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

👋 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.