Skip to content

[Awaiting Checklist] [$500] Some Categories Not Appearing in New Expensify After Migration #79936

Closed

Description

@m-natarajan

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:
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

Action Performed:

  1. Log in to Expensify Classic
  2. Create a new workspace and set it as your default
  3. Go to Categories > 'Import from Spreadsheet'
  4. Upload this spreadsheet
  5. Transition to New Expensify
  6. Click Create expense > Manual
  7. Open the Category dropdown

Expected Result:

All workspace categories that appear in Expensify Classic should also appear in New Expensify.

Actual Result:

Only a partial list of categories is displayed. No categories in the General & Administration top level category show.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022013997419162011432
  • Upwork Job ID: 2013997419162011432
  • Last Price Increase: 2026-01-27
  • Automatic offers:
    • aimane-chnaif | Reviewer | 110353851
Issue OwnerCurrent Issue Owner: @aimane-chnaif

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 19, 2026
  2. melvin-bot commented on Jan 19, 2026

    @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. MelvinBot commented on Jan 19, 2026

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    📣 @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:

    1. Make sure you've read and understood the contributing guidelines.
    2. 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.
    3. 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.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed on Jan 21, 2026
  6. 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
  7. melvin-bot commented on Jan 21, 2026

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 21, 2026
  9. melvin-bot commented on Jan 21, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif (External)

  10. 41 remaining items

  11. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    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:

  13. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    @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]

  14. melvin-bot commented on Feb 23, 2026

    @melvin-bot

    @garrettmknight Whoops! This issue is 2 days overdue. Let's get this updated quick!

  15. garrettmknight commented on Feb 24, 2026

    @garrettmknight
    Contributor

    Payment Summary

  16. garrettmknight commented on Feb 24, 2026

    @garrettmknight
    Contributor

    @aimane-chnaif checklist please

  17. 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
  18. aimane-chnaif commented on Feb 24, 2026

    @aimane-chnaif
    Contributor

    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:

    1. Log in to Expensify Classic
    2. Create a new workspace and set it as your default
    3. Go to Categories > 'Import from Spreadsheet'
    4. Upload this spreadsheet
    5. Transition to New Expensify
    6. Click Create expense > Manual
    7. Open the Category dropdown
    8. Verify that all categories are displayed

    Do we agree 👍 or 👎

  19. twisterdotcom commented on Mar 19, 2026

    @twisterdotcom
    Contributor

    @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
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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions