Repository navigation
Closed
Closed
Feature
Copy link
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to productionExternalAdded to denote the issue can be worked on by a contributorAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewHas a PR in reviewWeeklyKSv2KSv2
Description
Part of the Support the unreported expense flow in NewDot project
Main issue: https://github.com/Expensify/Expensify/issues/495162
Doc section:
Project: https://github.com/Expensify/Expensify/issues/495162
Feature Description
This adds the Category field option to the unreported expenses. It also enables the Category field in the Create Expense flow from self-DM.
The category field is always tied to
- the workspace of the report that is set in the report field
OR - the default workspace if no report is set
OR - the default Category list if no default workspace and no report is set
Manual Test Steps
User with no group workspace
- Click on the + button at the bottom of the selfDM chat and then click
Create Expense - Add an amount and click
Next - Verify that in the Confirm details page, you have a
Categoryfield that is empty by default, and it is not required - Click on the Category field and verify that you see the upgrade path
- Now have an unreported expense with no Category set on it
- Click on the unreported expense and verify that you can see the
Categoryfield - Click on Category and verify that you see the upgrade path
User with group workspaces but no default workspace
- Have a user, a member of workspace A. The user has no default workspace
- Click on the + button at the bottom of the selfDM chat and then click
Create Expense - Add an amount and click
Next - Click on the Category field and verify that you can pick from the default Categories list
- Now have an unreported expense in the selfDM, with no Category set
- Click on the unreported expense and verify that you have the Category and the Report fields
- Click on the Category field and verify that you can select from the default Categories list. Select a category
- Click on the Report field and pick a report from workspace A
- Verify that the Category field updates according to the workspace A settings:
9.1. If the Category field is disabled in workspace A, then remove the category and hide the field
9.2. If the Category field is enabled and the selected value is not one of the workspace A categories, we show a violation
User with group workspaces and one of them set as the default workspace
Same as the previous test steps, but with the categories of the default workspace instead of the default Categories list
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021973772554524406797
- Upwork Job ID: 1973772554524406797
- Last Price Increase: 2025-10-02
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @dylanexpensifyMetadata
Metadata
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to productionExternalAdded to denote the issue can be worked on by a contributorAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewHas a PR in reviewWeeklyKSv2KSv2
Type
Projects
- StatusShow more project fieldsDone
Activity
[-]Add the Category field to the unreported expenses[/-][+][$250] Add the Category field to the unreported expenses[/+]melvin-bot commentedon Oct 2, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021973772554524406797
melvin-bot commentedon Oct 2, 2025
Current assignee @parasharrajat is eligible for the External assigner, not assigning anyone new.
[-][$250] Add the Category field to the unreported expenses[/-][+][CRITICAL] Add the Category field to the unreported expenses[/+]68 remaining items
melvin-bot commentedon Oct 29, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Oct 29, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Due for payment 2025-10-31] [Unreported] [$250] [CRITICAL] Enable the Category field to the unreported expenses[/-][+][Due for payment 2025-11-06] [Due for payment 2025-10-31] [Unreported] [$250] [CRITICAL] Enable the Category field to the unreported expenses[/+]melvin-bot commentedon Oct 30, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.40-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-11-06. 🎊
For reference, here are some details about the assignees on this issue:
[-][Due for payment 2025-11-06] [Due for payment 2025-10-31] [Unreported] [$250] [CRITICAL] Enable the Category field to the unreported expenses[/-][+][Due for payment 2025-11-06] [Unreported] [$250] [CRITICAL] Enable the Category field to the unreported expenses[/+]cristipaval commentedon Nov 3, 2025
Closing. It is being tracked here. @dylanexpensify will pay all issues in bulk when the project is done