Skip to content

Expense - "Missing category" violation disappears after moving expense to workspace report #72325

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.29-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: #71583
Email or phone of affected tester (no customers): snjodisjdosjdosjo@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 workspace chat.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create a new report.
  4. Go to self DM.
  5. Create an expense with amount 0.00.
  6. Open the expense thread.
  7. Click Report.
  8. Select the workspace report.

Expected Result:

"Missing category" violation will be shown.

Actual Result:

"Missing category" violation appears and disappears.

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 10, 2025
  2. melvin-bot commented on Oct 10, 2025

    @melvin-bot

    Triggered auto assignment to @RachCHopkins (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 10, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 10, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 10, 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. grgia commented on Oct 10, 2025

    @grgia
    Contributor

    @Gonals assigning you as this was linked to your PR #71583

  7. mountiny commented on Oct 10, 2025

    @mountiny
    Contributor

    Should have been fixed by a revert, closing as QA will retest #72321

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 10, 2025
  9. IuliiaHerets commented on Oct 13, 2025

    @IuliiaHerets

    @mountiny The issue is no longer reproducible.
    Device: Windows 11, Chrome
    Build: v9.2.29-5

    retest.mp4
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.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions