Skip to content

Expense - Amount limit and description requirement violation appear when expense is unreported #72866

Closed

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.2.33-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: #72457
Email or phone of affected tester (no customers): jnsoidjdsoijsiosjdo@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Account has self DM and a workspace.
  • Rules feature is enabled in workspace settings > More features.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Create a manual expense without description.
  4. Go to transaction thread.
  5. Click Category.
  6. Select Advertising.
  7. Go to workspace settings > Category.
  8. Click Advertising.
  9. Enable "Require description".
  10. Click "Flag amounts over" and enter amount lower than the expense amount in Step 3.
  11. Click Save.
  12. Go back to the transaction thread.
  13. Click Category.
  14. Deselect Advertising.
  15. Click Category.
  16. Select Advertising.

Expected Result:

"Amount over x/person category limit" and "Description required for selected category" violations will not appear when the expense is unreported in self DM.

Actual Result:

"Amount over x/person category limit" and "Description required for selected category" violations initially did not appear after changing the settings. The violations appear after reselecting Advertising category.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 17, 2025
  2. melvin-bot commented on Oct 17, 2025

    @melvin-bot

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

  3. melvin-bot commented on Oct 17, 2025

    @melvin-bot

    Triggered auto assignment to @AndrewGable (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Oct 17, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 17, 2025

    @github-actions
    Contributor

    👋 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.
  6. AndrewGable commented on Oct 17, 2025

    @AndrewGable
    Contributor

    Fixed by revert #72857

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions