[HOLD for payment 2023-11-02] Category IOU - Incorrect ordering of subcategories in the category menu

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

Prerequisites:
Account Setup https://sites.google.com/applausemail.com/applause-expensifyproject/guides/newdot-categories
Setting up categories 1) https://expensify.testrail.io/index.php?/tests/view/3767005
2) https://expensify.testrail.io/index.php?/tests/view/3767010

Steps:

1. Open https://staging.new.expensify.com/
   or app
2. Log in to your Employee account
3. Click on the FAB button
4. Click on 'Request Money'
5. Choose 'Manual' and add an amount
6. Click on the "Next" button
7. Select the configured WS
8. Click 'show more' and click on 'Category'

Expected Result:

Subcategories should be displayed laddered under each other with a space to the left

Actual Result:

The subcategory for the parent subcategory is not displayed in a ladder, but is displayed at the very end of the category list

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.78.0

Reproducible in staging?: Yes

Reproducible in production?: Yes

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6226514_1696541611456.Recording__434.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

@puneetlath Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[puneetlath]

@rezkiy37 would you want to look into this one? It does seem like there is an issue with multiple levels of nesting. For example, this is what I'm seeing on this policy titled Collect Policy (which I just added you to).

[rezkiy37]

Hi, I’m Michael (Mykhailo) from Callstack and I would like to work in this issue.