Skip to content

[$250] Rules - Multi tag is not applied to expenses when tag is not from the first level #81094

@jponikarchuk

Description

@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: 9.3.11-17
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80853
Email or phone of affected tester (no customers): yonghongkok2+sdjoisdjoisj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Workspace has imported independent tags.
  • Rules are enabled.
  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Rules.
  3. Click Add merchant rule.
  4. Click Merchant in "For expenses with:" > enter Apple > click Save.
  5. Click Tags.
  6. Select a tag (eg, Europe) that is not from the first level tag.
  7. Click Add merchant rule.
  8. Go to workspace chat.
  9. Create an expense with Apple as merchant.
  10. Open the expense.

Expected Result:

Europe tag will be auto applied.

Actual Result:

Europe tag is not auto applied.

This issue happens when the tag is not from the first level.

This issue also happens with Expense rules - https://staging.new.expensify.com/settings/rules.

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 OwnerCurrent Issue Owner: @
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022018813448955500132
  • Upwork Job ID: 2018813448955500132
  • Last Price Increase: 2026-02-03
Issue OwnerCurrent Issue Owner: @situchan

Metadata

Metadata

Labels

ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions