[Due for payment 2026-04-30] [$250] [Exploratory] Expense - Missing required label on confirm details page when use Dependent tags

[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.3.58-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-17825/folder/13176676/41237316/1320797108?sort=-identifier
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11/Chrome
App Component: Money Requests

Action Performed:

Preconditions: Workspace import multi-level tags Dependent, Import "Multilevel tags" and disable"These are independent tags" during import
toggle on " Members must tag all expenses"

1. Open the NewDot app
2. Navigate to the Workspace chat
3. Start creating a manual expense
4. Enter amount ->Confirm details page

Expected Result:

A required label display

Actual Result:

Missing required label

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

Dependent_-_Multi_Level_tags_NEWW.csv

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @hungvu193

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022044011590813856958
• Upwork Job ID: 2044011590813856958
• Last Price Increase: 2026-04-14

[MelvinBot]

Proposal

What is the root cause of that problem?

The "required" label for tags on the confirm details page is driven by each tag list's individual required field (TagsOptionsListUtils.ts:216), not by the policy-level requiresTag flag. This is inconsistent with how categories work — categories check policy.requiresCategory directly (MoneyRequestConfirmationList.tsx:430).

When "Members must tag all expenses" is toggled on, setPolicyRequiresTag sets both policy.requiresTag = true and required = true on each individual tag list. However, when the backend syncs tag data (e.g., via OpenPolicyTagsPage or an accounting integration sync), it can overwrite the tag lists without preserving the required field — resetting it to undefined/false. Since the confirm page only checks the individual tag list's required field and defaults to false, the "required" label disappears.

This is especially problematic for dependent tags because the per-tag-list "Required" toggle is hidden when hasDependentTags is true (WorkspaceViewTagsPage.tsx:373), so there's no manual workaround other than toggling the global setting off and on again.

What changes do you think we should make in order to solve the problem?

In getTagVisibility (TagsOptionsListUtils.ts:216), fall back to policy.requiresTag when the individual tag list's required is not set:

// Before
const isTagRequired = required ?? false;

// After
const isTagRequired = required ?? !!policy?.requiresTag;

This mirrors how categories use policy.requiresCategory and makes the tag "required" label resilient to backend data sync overwrites. The policy object is already available in getTagVisibility's parameters.

What alternative solutions did you explore? (Optional)

An alternative would be to fix the backend sync to always preserve the required field on tag lists. However, adding the policy.requiresTag fallback on the frontend is simpler, more resilient, and consistent with how categories already work.

Supporting evidence

• Bug location: TagsOptionsListUtils.ts:216 — const isTagRequired = required ?? false only checks the tag list's own field
• Category comparison: MoneyRequestConfirmationList.tsx:430 — const isCategoryRequired = !!policy?.requiresCategory && !isTypeInvoice uses the policy-level flag
• Label rendering: MoneyRequestConfirmationListFooter.tsx:1112 — rightLabel={isTagRequired ? translate('common.required') : ''} shows nothing when isTagRequired is false
• Toggle sets both: Policy/Tag.ts:1045-1063 — setPolicyRequiresTag correctly sets required on all tag lists, but this can be overwritten by subsequent backend syncs
• No manual workaround for dependent tags: WorkspaceViewTagsPage.tsx:373 — {!hasDependentTags && ( hides the per-tag "Required" toggle

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External)