Skip to content

[Due for payment 2025-12-05] Expense - Expense without category is grouped as "No category" when created offline #76084

Closed

Description

@mitarachim

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

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense without category.
  4. Open the expense report.
  5. Go offline.
  6. Create another expense without category.
  7. Go online.

Expected Result:

Expense without category should be grouped as "Uncategorized" when created offline.

Actual Result:

Expense without category is grouped as "No category" when created offline and it changes to "Uncategorized" when online.

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

Bug7013699_1764124595327.6.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Nov 26, 2025
  2. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Triggered auto assignment to @garrettmknight (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. github-actions commented on Nov 26, 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.
  4. melvin-bot commented on Nov 26, 2025

    @melvin-bot

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

  5. melvin-bot commented on Nov 26, 2025

    @melvin-bot

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

  6. IuliiaHerets commented on Nov 26, 2025

    @IuliiaHerets

    Issue is not reproduced anymore

    93fbd0e78cc655d313bbdc2cea829464.mp4
  7. JmillsExpensify commented on Nov 26, 2025

    @JmillsExpensify
    Contributor

    This one makes sense to prioritize.

  8. 7 remaining items

  9. TaduJR commented on Nov 26, 2025

    @TaduJR
    Contributor

    I am here

  10. melvin-bot commented on Nov 26, 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. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 28, 2025
  12. changed the title [-]Expense - Expense without category is grouped as "No category" when created offline[/-] [+][Due for payment 2025-12-05] Expense - Expense without category is grouped as "No category" when created offline[/+] on Nov 28, 2025
  13. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.65-6 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-12-05. 🎊

    For reference, here are some details about the assignees on this issue:

    • @shubham1206agra requires payment through NewDot Manual Requests
    • @TaduJR requires payment (Needs manual offer from BZ)
  14. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    @shubham1206agra @garrettmknight The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. trjExpensify commented on Dec 1, 2025

    @trjExpensify
    Contributor

    Can we close this, as it was taken care of in the PR for the report layout?

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 productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions