You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Number: 9.4.0-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/folder/13176687/test-cases/87590916 Email or phone of affected tester (no customers):testpayment935@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Windows 11 pro /Chrome App Component: Workspace Settings
Action Performed:
Precondition: Create a workspace with at least one Category and Tag.
Navigate to staging.new.expensify.com.
Go to Account > Expense Rules.
Click New Rule and configure it as follows:
If the expense contains: Merchant name = "Test"
Apply these updates: Category = "Advertising"
Apply these updates: Tag = Any tag
Click Save Rule.
Return to the workspace settings and edit both the Category and Tag that were selected in the rule.
Navigate back to Expense Rules and open the existing rule.
Notice that the RHP still displays the previously selected Category and Tag.
Open the Category field.
Notice that the previous Category is still selected.
Open the Tag field.
Notice that the previous Tag has been removed and no Tag is selected.
Go to the workspace chat.
Create an expense with the merchant name "Test", leaving both the Category and Tag fields empty.
Expected Result:
In Step 7, an error message should indicate that the Category and Tag configured in the rule are no longer valid.
In Steps 9 and 11, both Category and Tag should behave consistently since both values were modified.
In Step 13, the rule should not apply any Tag because "None" is not a valid Tag value.
Actual Result:
In Step 7, no error message is displayed even though the Category and Tag configured in the rule are no longer valid.
In Steps 9 and 11, the Category still displays the previously selected value, while the Tag is changed to "None".
In Step 13, the expense is created with the Tag set to "None" based on the rule.
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.4.0-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/folder/13176687/test-cases/87590916
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 pro /Chrome
App Component: Workspace Settings
Action Performed:
Precondition: Create a workspace with at least one Category and Tag.
Expected Result:
In Step 7, an error message should indicate that the Category and Tag configured in the rule are no longer valid.
In Steps 9 and 11, both Category and Tag should behave consistently since both values were modified.
In Step 13, the rule should not apply any Tag because "None" is not a valid Tag value.
Actual Result:
In Step 7, no error message is displayed even though the Category and Tag configured in the rule are no longer valid.
In Steps 9 and 11, the Category still displays the previously selected value, while the Tag is changed to "None".
In Step 13, the expense is created with the Tag set to "None" based on the rule.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug7173030_1780693846306.bandicam_2026-06-05_23-39-15-687.mp4
View all open jobs on GitHub