[Due for payment 2026-01-09] [$250] Importing Single-Level Tags Prompts User to Switch Tag Levels Even When Already Using SL Tags

[m-natarajan]

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.2.72-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @miljakljajic
Slack conversation (hyperlinked to channel name): #Convert

Action Performed:

1. Open any workspace
2. Navigate to Tags
3. Add multiple tags using the Add tag button
4. Navigate to More → Import Spreadsheet → Single level tags

Expected Result:

The system should detect that the workspace is already using single-level tags.
Import should proceed normally without prompting the user to switch tag level types.

Actual Result:

The import flow shows a warning asking the user to switch tag levels.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Recording.2031.mp4

2025-12-04_13-23-55.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021998058416186040043
• Upwork Job ID: 1998058416186040043
• Last Price Increase: 2025-12-22

Issue Owner

Current Issue Owner: @heyjennahay

[melvin-bot]

Triggered auto assignment to @heyjennahay (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.

[Nodebrute]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Importing Single-Level Tags Prompts User to Switch Tag Levels Even When Already Using SL Tags

What is the root cause of that problem?

Here we only check for visible tags when we press single level of tags

App/src/pages/workspace/tags/ImportTagsOptionsPage.tsx

Lines 195 to 196 in 68d4da3

	if (hasVisibleTags) {
	setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);

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

We should also check for isMultiLevelTags here

App/src/pages/workspace/tags/ImportTagsOptionsPage.tsx

Line 195 in 68d4da3

if (hasVisibleTags) {

We can do something like this

  if (hasVisibleTags && isMultiLevelTags) {
                                setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);
                            } 

What alternative solutions did you explore? (Optional)

We can also simply just check for isMultiLevelTags

  if (isMultiLevelTags) {
                                setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);
                            } 

[ChavdaSachin]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Importing Single-Level Tags Prompts User to Switch Tag Levels Even When Already Using SL Tags

What is the root cause of that problem?

Following snippet only checks if any visible tags are available and prompts with switch tag levels modal.

App/src/pages/workspace/tags/ImportTagsOptionsPage.tsx

Lines 195 to 196 in 68d4da3

	if (hasVisibleTags) {
	setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);

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

Currently switch tag levels serves 2 purposes for single level tags import.

1. display a warning that - existing tags would be lost
2. clear the existing tags when user clicks switch tag levels button on the warning modal.

So to fix this - we need to add new confirmation modal to warn user about removal of existing tags and perform cleanup once user confirms - similar to what we do for multi level tags

App/src/pages/workspace/tags/ImportTagsOptionsPage.tsx

Lines 252 to 271 in 68d4da3

	<ConfirmModal
	isVisible={isOverridingMultiTag}
	onConfirm={() => {
	setIsOverridingMultiTag(false);
	Navigation.navigate(
	isQuickSettingsFlow
	? ROUTES.SETTINGS_TAGS_IMPORT.getRoute(policyID, ROUTES.SETTINGS_TAGS_ROOT.getRoute(policyID, backTo))
	: ROUTES.WORKSPACE_TAGS_IMPORT.getRoute(policyID),
	);
	}}
	title={translate('workspace.tags.overrideMultiTagWarning.title')}
	prompt={overrideMultiTagPrompt}
	confirmText={translate('workspace.tags.overrideMultiTagWarning.title')}
	danger
	cancelText={translate('common.cancel')}
	onCancel={() => {
	setIsOverridingMultiTag(false);
	setImportedSpreadsheetIsImportingMultiLevelTags(false);
	}}
	/>

App/src/pages/workspace/tags/ImportTagsOptionsPage.tsx

Lines 76 to 81 in 68d4da3

	if (hasVisibleTags) {
	if (isMultiLevelTags) {
	setIsOverridingMultiTag(true);
	} else {
	setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);
	}

Or reuse the current isOverridingMultiTag confirmation modal if we can.(could be decided during PR phase)

and display the isOverridingSingleLevelTags warning modal when user wants to import single level tags while current tags are also single level

    if (hasVisibleTags) {
        if(!isMultiLevelTags){
            setIsOverridingSingleLevelTags(true);
            return;
        }
        setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);
    } else {

App/src/pages/workspace/tags/ImportTagsOptionsPage.tsx

Lines 194 to 197 in 68d4da3

	setImportedSpreadsheetIsImportingMultiLevelTags(false);
	if (hasVisibleTags) {
	setIsSwitchSingleToMultipleLevelTagWarningModalVisible(true);
	} else {

And if we agree upon any small expectations those also should be delt with during PR phase.

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021998058416186040043

[melvin-bot]

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