Skip to content

[Due for payment 2025-11-06] [Unreported] [$250] [CRITICAL] Enable the Category field to the unreported expenses #71784

Closed

Description

@cristipaval

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

  1. Click on the + button at the bottom of the selfDM chat and then click Create Expense
  2. Add an amount and click Next
  3. Verify that in the Confirm details page, you have a Category field that is empty by default, and it is not required
  4. Click on the Category field and verify that you see the upgrade path
  5. Now have an unreported expense with no Category set on it
  6. Click on the unreported expense and verify that you can see the Category field
  7. Click on Category and verify that you see the upgrade path

User with group workspaces but no default workspace

  1. Have a user, a member of workspace A. The user has no default workspace
  2. Click on the + button at the bottom of the selfDM chat and then click Create Expense
  3. Add an amount and click Next
  4. Click on the Category field and verify that you can pick from the default Categories list
  5. Now have an unreported expense in the selfDM, with no Category set
  6. Click on the unreported expense and verify that you have the Category and the Report fields
  7. Click on the Category field and verify that you can select from the default Categories list. Select a category
  8. Click on the Report field and pick a report from workspace A
  9. 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 OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 2, 2025
  2. changed the title [-]Add the Category field to the unreported expenses[/-] [+][$250] Add the Category field to the unreported expenses[/+] on Oct 2, 2025
  3. melvin-bot commented on Oct 2, 2025

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 2, 2025
  5. melvin-bot commented on Oct 2, 2025

    @melvin-bot

    Current assignee @parasharrajat is eligible for the External assigner, not assigning anyone new.

  6. changed the title [-][$250] Add the Category field to the unreported expenses[/-] [+][CRITICAL] Add the Category field to the unreported expenses[/+] on Oct 2, 2025
  7. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 2, 2025
  8. 68 remaining items

  9. melvin-bot commented on Oct 29, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  10. melvin-bot commented on Oct 29, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  11. changed the title [-][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[/+] on Oct 30, 2025
  12. melvin-bot commented on Oct 30, 2025

    @melvin-bot

    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:

    • @MrMuzyk does not require payment (Contractor)
    • @parasharrajat requires payment through NewDot Manual Requests
    • @koko57 does not require payment (Contractor)
  13. changed the title [-][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[/+] on Nov 3, 2025
  14. cristipaval commented on Nov 3, 2025

    @cristipaval
    ContributorAuthor

    Closing. It is being tracked here. @dylanexpensify will pay all issues in bulk when the project is done

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions