You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-12-05] Expense - Expense without category is grouped as "No category" when created offline #76084
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:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense without category.
Open the expense report.
Go offline.
Create another expense without category.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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:
@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]
Activity
melvin-bot commentedon Nov 26, 2025
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.github-actions commentedon Nov 26, 2025
👋 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:
melvin-bot commentedon Nov 26, 2025
Triggered auto assignment to @francoisl (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 26, 2025
💬 A slack conversation has been started in #expensify-open-source
IuliiaHerets commentedon Nov 26, 2025
Issue is not reproduced anymore
93fbd0e78cc655d313bbdc2cea829464.mp4
JmillsExpensify commentedon Nov 26, 2025
This one makes sense to prioritize.
7 remaining items
TaduJR commentedon Nov 26, 2025
I am here
melvin-bot commentedon Nov 26, 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.
[-]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[/+]melvin-bot commentedon Nov 28, 2025
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:
melvin-bot commentedon Nov 28, 2025
@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]
trjExpensify commentedon Dec 1, 2025
Can we close this, as it was taken care of in the PR for the report layout?