Deleting parent category and assigning a child as its replacement creates phantom category.

[JReko]

For example:

• Category 1
• Category 2
• Category 3
  • Category 4

Deleting category 3 and selecting category 4 as its replacement will delete category 3 and make category 4 disappear. Reason is simple. Category 4 now has its own ID as a ParentCategoryID.

Solution could be fixing the attribution of the ParentCategoryID or preventing child categories from being a replacement option when we delete a parent category.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[JReko]

I'm removing the stale label on this one, until someone explicitly says we don't want to fix it. Granted it's probably low on priority but this bug can/will probably lead to awful user experience, support tickets, support investigations, dev investigations, dev manual database fixes. The scope is fairly small and a short amount of time would be spent fixing it. Balancing out the cost of fixing it versus the cost of the bug happening the a few times, I think we already win.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.