[Due for payment 2026-02-26] Expense - Tag not enabled workspace shows tags via edit multiple without violation.

[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: V9.2.21-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: #76264
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

1. Launch app
2. Create 2 workspace
3. Create 2 distance manual expense in both workspace
4. In default workspace, add a category and tag
5. Go to reports - expense
6. Select all expenses - edit multiple
7. Set category and tag which is added in step 4 and save
8. Open the expense with category not valid
9. Open the expense details page
10. Note tag is set
11. Go to workspace settings and note tag is not enabled in that workspace

Expected Result:

Tag not enabled workspace shows tags via edit multiple must show violation.

Actual Result:

Tag not enabled workspace shows tags via edit multiple without violation.

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 Owner

Current Issue Owner: @jliexpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @jliexpensify (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]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #76264 - "Feat: bulk edit multiple" by @waterim (High confidence)
Related Issues: None

Recommendation: REVERT

PR #76264 introduced the bulk edit multiple feature but does not properly trigger violation checks when tags from one workspace are applied to expenses in another workspace. The violation logic exists in ViolationsUtils.ts but is not being properly invoked or provided the correct policy context during bulk edit operations.

Labels: Issue reproduced on staging only and not on production (new feature). Keeping DeployBlockerCash label as this is a frontend bug requiring App changes. No label changes made.

Detailed Analysis

Evidence

PR #76264 added the bulk edit multiple expenses feature. The issue describes that when using "Edit multiple" to apply tags across workspaces, expenses show the wrong workspace tags without triggering the expected "tagOutOfPolicy" violation.

The PR test plan even acknowledges this scenario:

Test 3: Cross-policy bulk edit
Pick a category from the active workspace list
Verify category applied to all expenses (transactions on the other workspace may show a violation — thats expected)

However, per the bug report, violations are NOT being shown as expected.

Verification

• ViolationsUtils.ts (lines 46-84, 175-194) contains comprehensive tag violation logic including getTagViolationsForSingleLevelTags and getTagViolationsForMultiLevelTags
• The violation checking function getViolationsOnyxData properly handles tagOutOfPolicy violations by checking if updatedTransaction.tag exists in the policy tags
• The new bulk edit feature added updateMultipleMoneyRequests function which updates multiple transactions but appears to not properly invoke violation checks or pass the correct per-transaction policy context

Root Cause

When bulk editing transactions across multiple workspaces, the implementation likely:

1. Uses a single policy context (active workspace) instead of each transactions own workspace policy
2. Does not call ViolationsUtils.getViolationsOnyxData for each updated transaction with the correct policy
3. This causes the tag validation to either be skipped or check against the wrong policys tags

The result is that tags get applied without triggering the client-side violation that should flag them as "tagOutOfPolicy".