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
[Awaiting Checklist] [$500] Some Categories Not Appearing in New Expensify After Migration #79936
Version Number: Reproducible in staging?: Needs Reproduction (Unable to reproduce) Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from BrowserStack: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@kiadd Slack conversation (hyperlinked to channel name): #Expensify Bugs
📣 @DGephart! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
changed the title [-]Some Categories Not Appearing in New Expensify After Migration[/-][+][$250] Some Categories Not Appearing in New Expensify After Migration[/+]on Jan 21, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.18-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@aimane-chnaif@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]
changed the title [-][Due for payment 2026-02-20] [$500] Some Categories Not Appearing in New Expensify After Migration[/-][+][Awaiting Checklist] [$500] Some Categories Not Appearing in New Expensify After Migration[/+]on Feb 24, 2026
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: The root cause is in OD / backend. There's no such case in ND when creating/updating categories.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Jan 19, 2026
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.MelvinBot commentedon Jan 19, 2026
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
melvin-bot commentedon Jan 20, 2026
📣 @DGephart! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
[-]Some Categories Not Appearing in New Expensify After Migration[/-][+][$250] Some Categories Not Appearing in New Expensify After Migration[/+]melvin-bot commentedon Jan 21, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022013997419162011432
melvin-bot commentedon Jan 21, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif (
External)41 remaining items
melvin-bot commentedon Feb 13, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 13, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.18-8 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 2026-02-20. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 13, 2026
@aimane-chnaif @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]
melvin-bot commentedon Feb 23, 2026
@garrettmknight Whoops! This issue is 2 days overdue. Let's get this updated quick!
garrettmknight commentedon Feb 24, 2026
Payment Summary
garrettmknight commentedon Feb 24, 2026
@aimane-chnaif checklist please
[-][Due for payment 2026-02-20] [$500] Some Categories Not Appearing in New Expensify After Migration[/-][+][Awaiting Checklist] [$500] Some Categories Not Appearing in New Expensify After Migration[/+]aimane-chnaif commentedon Feb 24, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: The root cause is in OD / backend. There's no such case in ND when creating/updating categories.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
twisterdotcom commentedon Mar 19, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-1791-a703-81b0-ee1e8f655424