[$250] Expense - Category field is missing while submitting track expense to workspace.

[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.2-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-704/folder/13176877/41237352/881815553
Email or phone of affected tester (no customers): ibellicotest+1727@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.
Prerequisite 2: Account has a Self DM.

1. Open the Expensify app.
2. Create a manual expense and submit it to Self DM.
3. Once redirected to chat, tap on "Submit it to someone" below the expense.
4. Select any workspace to submit the expense to.
5. On confirmation page, note that category field is missing.
6. Add a merchant and submit the expense.
7. Once navigated to workspace chat, open the expense.
8. Note that a "Missing Category" error appears.

Expected Result:

User should be able to add a category to a track expense when submitting it to a workspace chat.

Actual Result:

"Category" and "Reimbursable" fields are missing while submitting a track expense to a workspace chat. After the expense is submitted, a "Missing Category" error message appears on report.

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

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021964410729148785816
• Upwork Job ID: 1964410729148785816
• Last Price Increase: 2025-09-06

Issue Owner

Current Issue Owner: @allroundexperts

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

👋 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.